Edit

Quickstart: Deploy Events using the Azure portal

  • Article
  • 2 minutes to read

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®) and DICOM event messages.

Prerequisites

It's important that you have the following prerequisites completed before you begin the steps of deploying the Events feature in Azure Health Data Services.

Important

You will also need to make sure that the Microsoft.EventGrid resource provider has been successfully registered with your Azure subscription to deploy the Events feature. For more information, see Azure resource providers and types - Register resource provider.

Note

For the purposes of this quickstart, we'll be using a basic Events set up and an event hub as the endpoint for Events messages. To learn how to deploy Azure Event Hubs, see Quickstart: Create an event hub using Azure portal.

Deploy Events

  1. Browse to the workspace that contains the FHIR or DICOM service you want to send Events messages from and select the Events button on the left hand side of the portal.

    Screenshot of workspace and select Events button.

  2. Select + Event Subscription to begin the creation of an event subscription.

    Screenshot of workspace and select events subscription button.

  3. In the Create Event Subscription box, enter the following subscription information.

    • Name: Provide a name for your Events subscription.
    • System Topic Name: Provide a name for your System Topic.

    Note

    The first time you set up the Events feature, you will be required to enter a new System Topic Name. Once the system topic for the workspace is created, the System Topic Name will be used for any additional Events subscriptions that you create within the workspace.

    • Event types: Type of FHIR or DICOM events to send messages for (for example: create, updated, and deleted).
    • Endpoint Details: Endpoint to send Events messages to (for example: an Azure Event Hubs namespace + an event hub).

    Note

    For the purposes of this quickstart, we'll use the Event Schema and the Managed Identity Type settings at their default values.

    Screenshot of the create event subscription box.

  4. After the form is completed, select Create to begin the subscription creation.

  5. Event messages won't be sent until the Event Grid System Topic deployment has successfully completed. Upon successful creation of the Event Grid System Topic, the status of the workspace will change from "Updating" to "Succeeded".

    Screenshot of an events subscription being deployed

    Screenshot of an events subscription successfully deployed.

  6. After the subscription is deployed, it will require access to your message delivery endpoint.

    Screenshot of a successfully deployed events subscription.

    Tip

    For more information about providing access using an Azure Managed identity, see Assign a system-managed identity to an Event Grid system topic and Event delivery with a managed identity

    For more information about managed identities, see What are managed identities for Azure resources

    For more information about Azure role-based access control (Azure RBAC), see What is Azure role-based access control (Azure RBAC)

Next steps

In this article, you've learned how to deploy events in the Azure portal. For details about supported events, see Azure Health Data Services as an Event Grid source.

To learn how to enable the Events metrics, see

How to use Events metrics

To learn how to export Event Grid system diagnostic logs and metrics, see

How to enable Events diagnostic logs and metrics

FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.