Skip to content

Support for import configuration in azurerm_healthcare_fhir_service #28761

@LCARyanKing

Description

@LCARyanKing

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Description

The Azure FHIR Service has options for configuring an Import mode to allow ingestion of FHIR resources from a Storage Account. In addition to the flag to enable Imports, there are options for specifying the Storage Account (integrationDataStore) and the mode of operation of the import (initial vs incremental). These settings are detailed here:

https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/configure-import-data#step-3-set-the-import-configuration-of-the-fhir-service

It would be helpful if the azurerm_healthcare_fhir_service Terraform resource included the ability to configure and manage these options.

New or Affected Resource(s)/Data Source(s)

azurerm_healthcare_fhir_service

Potential Terraform Configuration

resource "azurerm_healthcare_fhir_service" "example" {
  name                = "tfexfhir"
  location            = "east us"
  resource_group_name = "tfex-resource_group"
  workspace_id        = azurerm_healthcare_workspace.example.id
  kind                = "fhir-R4"

  // ... other options omitted for brevity

  import {
    enabled = true
    initial_import_mode = true
    integration_data_store = "example-import-storage-account-name"
  }
}

References

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions