Merge pull request #203919 from msjasteppe/events-disclosure-update

Adding new disclaimer banner and edits.

Author: v-stsavell

articles/healthcare-apis/events/events-consume-logic-apps.md

@@ -6,13 +6,13 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
-ms.date: 05/26/2022
+ms.date: 07/06/2022
 ms.author: v-smcevoy
 ---
 
 # Consume events with Logic Apps
 
-This tutorial shows how to use Azure Logic Apps to process Azure Health Data Services FHIR events. Logic Apps create and run automated workflows to process event data from other applications. You will learn how to register a FHIR event with your Logic App, meet a specified event criteria, and perform a service operation.
+This tutorial shows how to use Azure Logic Apps to process Azure Health Data Services Fast Healthcare Interoperability Resources (FHIR®) events. Logic Apps create and run automated workflows to process event data from other applications. You will learn how to register a FHIR event with your Logic App, meet a specified event criteria, and perform a service operation.
 
 Here's an example of a Logic App workflow:
 
@@ -344,4 +344,4 @@ For more information about FHIR events, see
 >[!div class="nextstepaction"]
 >[What are Events?](./events-overview.md)
 
-(FHIR®) is a registered trademark of HL7 and is used with the permission of HL7.
+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/events/events-deploy-portal.md

@@ -1,16 +1,16 @@
 ---
-title: Deploy Events in the Azure portal - Azure Health Data Services
+title: Deploy Events using the Azure portal - Azure Health Data Services
 description: This article describes how to deploy the Events feature in the Azure portal.
 services: healthcare-apis
 author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 03/21/2022
+ms.date: 07/06/2022
 ms.author: jasteppe
 ---
 
-# Deploy Events in the Azure portal
+# Deploy Events using the Azure portal
 
 In this quickstart, you’ll learn how to deploy the Azure Health Data Services Events feature in the Azure portal to send Fast Healthcare Interoperability Resources (FHIR®) event messages.
 
@@ -88,4 +88,4 @@ To learn how to export Event Grid system diagnostic logs and metrics, see
 >[!div class="nextstepaction"]
 >[How to export Events diagnostic logs and metrics](./events-display-metrics.md)
 
-FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
+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/events/events-disable-delete-workspace.md

@@ -1,22 +1,22 @@
 ---
-title: Disable Events and delete workspaces - Azure Health Data Services
+title: Disable events and delete workspaces - Azure Health Data Services
 description: This article provides resources on how to disable Events and delete workspaces.
 services: healthcare-apis
 author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
-ms.date: 03/22/2022
+ms.date: 07/06/2022
 ms.author: jasteppe
 ---
 
-# Disable Events and delete workspaces
+# Disable events and delete workspaces
 
-In this article, you'll learn how to disable Events and delete workspaces in Azure Health Data Services.
+In this article, you'll learn how to disable the Events feature and delete workspaces in the Azure Health Data Services.
 
-## Disable Events
+## Disable events
 
-To disable Events from sending event messages for a single Event Subscription, the Event Subscription must be deleted.
+To disable events from sending event messages for a single Event Subscription, the Event Subscription must be deleted.
 
 1. Select the Event Subscription to be deleted. In this example, we'll be selecting an Event Subscription named **fhir-events**.
 
@@ -51,4 +51,4 @@ For more information about how to troubleshoot Events, see
 >[!div class="nextstepaction"]
 >[Troubleshoot Events](./events-troubleshooting-guide.md)
 
-(FHIR®) is a registered trademark of HL7 and is used with the permission of HL7.
+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/events/events-display-metrics.md

@@ -6,7 +6,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
-ms.date: 03/22/2022
+ms.date: 07/06/2022
 ms.author: jasteppe
 ---
 
@@ -42,4 +42,4 @@ To learn how to export Events Azure Event Grid system diagnostic logs and metric
 >[!div class="nextstepaction"]
 >[Configure Events diagnostic logs and metrics exporting](./events-export-logs-metrics.md)
 
-(FHIR®) is a registered trademark of HL7 and is used with the permission of HL7.
+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/events/events-export-logs-metrics.md

@@ -6,7 +6,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
-ms.date: 03/22/2022
+ms.date: 07/06/2022
 ms.author: jasteppe
 ---
 
@@ -25,7 +25,7 @@ After they're configured, Event Grid system topics diagnostic logs and metrics w
 |View a list of currently captured Event Grid system topics metrics.|[Event Grid system topic metrics](../../azure-monitor/essentials/metrics-supported.md#microsofteventgridsystemtopics)| 
 |More information about how to work with diagnostics logs.|[Azure Resource Log documentation](../../azure-monitor/essentials/platform-logs-overview.md)|
 
-> [!Note] 
+> [!NOTE] 
 > It might take up to 15 minutes for the first Events diagnostic logs and metrics to display in the destination of your choice.  
 
 ## Next steps
@@ -35,4 +35,4 @@ To learn how to display Events metrics in the Azure portal, see
 >[!div class="nextstepaction"]
 >[How to display Events metrics](./events-display-metrics.md)
 
-(FHIR®) is a registered trademark of HL7 and is used with the permission of HL7.
+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/events/events-faqs.md

@@ -6,7 +6,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: reference
-ms.date: 03/02/2022
+ms.date: 07/06/2022
 ms.author: jasteppe
 ---
 
@@ -18,7 +18,7 @@ The following are some of the frequently asked questions about Events.
 
 ### Can I use Events with a different FHIR service other than the Azure Health Data Services FHIR service?
 
-No. The Azure Health Data Services Events feature only currently supports the Azure Health Data Services FHIR service.
+No. The Azure Health Data Services Events feature only currently supports the Azure Health Data Services Fast Healthcare Interoperability Resources (FHIR®) service.
 
 ### What FHIR resource events does Events support?
 
@@ -42,25 +42,22 @@ The throughput of FHIR events is governed by the throughput of the FHIR service
 
 ### How am I charged for using Events?
 
-There are no extra charges for using Azure Health Data Services Events. However, applicable charges for the [Event Grid](https://azure.microsoft.com/pricing/details/event-grid/) might be assessed against your Azure subscription.
-
+There are no extra charges for using [Azure Health Data Services Events](https://azure.microsoft.com/pricing/details/health-data-services/). However, applicable charges for the [Event Grid](https://azure.microsoft.com/pricing/details/event-grid/) will be assessed against your Azure subscription.
 
 ### How do I subscribe to multiple FHIR services in the same workspace separately?
 
 You can use the Event Grid filtering feature. There are unique identifiers in the event message payload to differentiate different accounts and workspaces. You can find a global unique identifier for workspace in the `source` field, which is the Azure Resource ID. You can locate the unique FHIR account name in that workspace in the `data.resourceFhirAccount` field. When you create a subscription, you can use the filtering operators to select the events you want to get in that subscription.
 
   :::image type="content" source="media\event-grid\event-grid-filters.png" alt-text="Screenshot of the Event Grid filters tab." lightbox="media\event-grid\event-grid-filters.png":::
 
-
 ### Can I use the same subscriber for multiple workspaces or multiple FHIR accounts?
 
-Yes. We recommend that you use different subscribers for each individual FHIR accounts to process in isolated scopes.
+Yes. We recommend that you use different subscribers for each individual FHIR account to process in isolated scopes.
 
 ### Is Event Grid compatible with HIPAA and HITRUST compliance obligations?
 
 Yes. Event Grid supports customer's Health Insurance Portability and Accountability Act (HIPAA) and Health Information Trust Alliance (HITRUST) obligations. For more information, see [Microsoft Azure Compliance Offerings](https://azure.microsoft.com/resources/microsoft-azure-compliance-offerings/).
 
-
  ### What is the expected time to receive an Events message?
 
 On average, you should receive your event message within one second after a successful HTTP request. 99.99% of the event messages should be delivered within five seconds unless the limitation of either the FHIR service or [Event Grid](../../event-grid/quotas-limits.md) has been met.
@@ -69,7 +66,6 @@ On average, you should receive your event message within one second after a succ
 
 Yes. The Event Grid guarantees at least one Events message delivery with its push mode. There may be chances that the event delivery request returns with a transient failure status code for random reasons. In this situation, the Event Grid will consider that as a delivery failure and will resend the Events message. For more information, see [Azure Event Grid delivery and retry](../../event-grid/delivery-and-retry.md).
 
-
 Generally, we recommend that developers ensure idempotency for the event subscriber. The event ID or the combination of all fields in the ```data``` property of the message content are unique per each event. The developer can rely on them to de-duplicate. 
 
 ## More frequently asked questions
@@ -81,4 +77,4 @@ Generally, we recommend that developers ensure idempotency for the event subscri
 
 [FAQs about Azure Health Data Services MedTech service](../iot/iot-connector-faqs.md)
 
-(FHIR®) is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
+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/events/events-message-structure.md

@@ -6,7 +6,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: reference
-ms.date: 03/22/2022
+ms.date: 07/06/2022
 ms.author: jasteppe
 ---
 
@@ -15,7 +15,7 @@ ms.author: jasteppe
 In this article, you'll learn about the Events message structure, required and non-required elements, and you'll be provided with samples of Events message payloads.
 
 > [!IMPORTANT]
-> Events currently supports only the following FHIR resource operations:
+> Events currently supports only the following Fast Healthcare Interoperability Resources (FHIR®) resource operations:
 >
 > - **FhirResourceCreated** - The event emitted after a FHIR resource gets created successfully.
 >
@@ -25,7 +25,6 @@ In this article, you'll learn about the Events message structure, required and n
 >
 > For more information about the FHIR service delete types, see [FHIR REST API capabilities for Azure Health Data Services FHIR service](../../healthcare-apis/fhir/fhir-rest-api-capabilities.md)
 
-
 ## Events message structure
 
 |Name|Type|Required|Description|
@@ -178,4 +177,4 @@ For more information about deploying Events, see
 >[!div class="nextstepaction"]
 >[Deploying Events in the Azure portal](./events-deploy-portal.md)
 
-(FHIR®) is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
+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/events/events-overview.md

@@ -6,7 +6,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: overview
-ms.date: 04/06/2022
+ms.date: 07/06/2022
 ms.author: jasteppe
 ---
 
@@ -53,7 +53,7 @@ Use Events to send FHIR resource change messages to services like [Azure Event H
 
 ## Secure
 
-Built on a platform that supports protected health information (PHI) and personal identifiable information (PII) data compliance with privacy, safety, and security in mind, the Events messages do not transmit sensitive data as part of the message payload.
+Built on a platform that supports protected health information and customer content data compliance with privacy, safety, and security in mind, the Events messages do not transmit sensitive data as part of the message payload.
 
 Use [Azure Managed identities](../../active-directory/managed-identities-azure-resources/overview.md) to provide secure access from your Event Grid system topic to the Events message receiving endpoints of your choice. 
 
@@ -62,7 +62,7 @@ Use [Azure Managed identities](../../active-directory/managed-identities-azure-r
 For more information about deploying Events, see
 
 >[!div class="nextstepaction"]
->[Deploying Events in the Azure portal](./events-deploy-portal.md)
+>[Deploying Events using the Azure portal](./events-deploy-portal.md)
 
 For frequently asks questions (FAQs) about Events, see
 
@@ -74,4 +74,4 @@ For Events troubleshooting resources, see
 >[!div class="nextstepaction"]
 >[Events troubleshooting guide](./events-troubleshooting-guide.md)
 
-(FHIR®) is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
+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/events/events-troubleshooting-guide.md

@@ -6,7 +6,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: troubleshooting
-ms.date: 03/14/2022
+ms.date: 07/06/2022
 ms.author: jasteppe
 ---
 # Troubleshoot Events
@@ -15,7 +15,7 @@ This article provides guides and resources to troubleshoot Events.
 
 > [!IMPORTANT]
 >
-> FHIR resource change data is only written and event messages are sent when the Events feature is turned on. The Event feature doesn't send messages on past FHIR resource changes or when the feature is turned off.
+> Fast Healthcare Interoperability Resources (FHIR®) resource change data is only written and event messages are sent when the Events feature is turned on. The Event feature doesn't send messages on past FHIR resource changes or when the feature is turned off.
 
 :::image type="content" source="media/events-overview/events-overview-flow.png" alt-text="Diagram of data flow from users to a FHIR service and then into the Events pipeline" lightbox="media/events-overview/events-overview-flow.png":::
 
@@ -40,7 +40,7 @@ Use this resource to learn about the Events message structure, required and non-
 ### How to
 
 Use this resource to learn how to deploy Events in the Azure portal: 
-* [How to deploy Events in the Azure portal](./events-deploy-portal.md)
+* [How to deploy Events using the Azure portal](./events-deploy-portal.md)
 
 >[!Important]
 >The Event Subscription requires access to whichever endpoint you chose to send Events messages to. For more information, see [Enable managed identity for a system topic](../../event-grid/enable-identity-system-topics.md).
@@ -61,4 +61,4 @@ To learn about frequently asked questions (FAQs) about Events, see
 >[!div class="nextstepaction"]
 >[Frequently asked questions about Events](./events-faqs.md)
 
-(FHIR®) is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
+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/events/index.yml

@@ -1,7 +1,7 @@
 ### YamlMime:Landing
 
 title: Events
-summary: Events documentation page for Azure Health Data Services . 
+summary: Events documentation page for Azure Health Data Services. 
 
 metadata:
   title: Azure Health Data Services MedTech service
@@ -13,7 +13,7 @@ metadata:
   ms.collection: collection
   author: msjasteppe
   ms.author: jasteppe
-  ms.date: 03/22/2022
+  ms.date: 07/06/2022
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
 
@@ -30,7 +30,7 @@ landingContent:
     linkLists:
       - linkListType: quickstart
         links:
-          - text: Deploy Events in the Azure portal
+          - text: Deploy Events using the Azure portal
             url: events-deploy-portal.md
 
   - title: Events message structure