Configure virtual health data tables

You can optimize your cloud hosting spend with the virtual health data tables feature in Microsoft Cloud for Healthcare. This feature helps you virtualize your clinical reference data and other healthcare data when using model-driven apps and other engagement solutions. Virtualizing your data removes the need for building expensive integrations that visualize the same data intensive tables multiple times across Microsoft and third-party applications such as electronic health record (EHR) systems.


Virtual health data tables target core functionality in connecting Microsoft Cloud for Healthcare to external FHIR (Fast Healthcare Interoperability Resources) servers. This article assumes you have a FHIR server, and the November 2021 release or a higher release of Microsoft Cloud for Healthcare. In addition, this article also assumes you've completed the following steps:

  • Configured patients to flow into Dataverse using the Data integration toolkit.
  • Deployed an Azure Logic App via the Healthcare data pipeline template.
  • Set up a managed identity in Azure (client ID and client secret) with permissions to the FHIR server.
  • Configured the managed identity in the Data integration toolkit.
  • Set up the virtual data source attributes (FHIR Server URL, Auth, and Resource).
  • Switched the Encounter and Observation data routes to virtual.

For more information about completing these steps, go to Overview of Dataverse healthcare APIs.

Implementation details

The tables that support virtual health data tables are configured to route to Dataverse by default. To switch the data store to virtual and route data requests to the FHIR server, follow these steps in the Data integration toolkit:

  1. Configure security roles for admins and virtual table users.

    • Assign the new Healthcare Virtual Tables Admin security role to the admins configuring the virtual tables. Make sure these admins also have the Sync admin for FHIR Config Administrator role, as explained in Data integration toolkit security roles.

    • Assign the new Healthcare Virtual Tables User security role to everyone who needs access to the virtual table entities.

  2. Configure connectivity to the FHIR server with the following fields:

    • Provider client ID and client secret
    • Microsoft healthcare data source
  3. Update data routes for the selected tables. Only Observation and Encounter related tables are in scope for virtual health data tables. These records have read-only access.

Update FHIR server client ID and client secret

  1. In the Data integration toolkit, navigate to Integration settings, and select Virtual Health Data Tables.

    A screenshot displaying the integration settings.

  2. Enter the Client ID and Client Secret for the FHIR server in the provided fields.

  3. Enter the Server URL and Authority URL for the target FHIR server.

  4. Select the desired value for Logging Level.

  5. Select Save to commit your changes.

Perform the same steps when updating a Client Secret when it expires or is newly generated.

Update data route to Dataverse or virtual

Data routes offer the ability to dynamically change the data provider for virtual tables. To switch the data route for tables from virtual to Dataverse or vice versa, perform the following steps:

  1. In the Data integration toolkit, navigate to Data Routes under Map Setup.

  2. Select one of the available data route records, such as Observation or Encounter, and select Edit.

    A screenshot displaying the observation table.

  3. Change the value for the Data Provider to Use field. You receive a message prompt with a confirmation.

    A screenshot displaying the data provider change confirmation message.

  4. After you select Confirm Change on the message, you can select the entity map for this route.

    A screenshot showing the entity map selection.

  5. This update also updates each data route for the corresponding expansion tables. The Data Provider to Use values are updated and the correct entity map is assigned.

  6. To validate your changes, change the navigation area to Healthcare Data and select the corresponding navigation item under Clinical Data for your selected virtual table. Based on your selection, the data presented in this view should now be sourced from either Dataverse or virtual.

For some examples on virtual health data table capabilities, go to Use virtual health data tables.

See also

What is Microsoft Cloud for Healthcare?
Overview of Data integration toolkit
Overview of virtual health data tables
Use virtual health data tables