Skip to content

Latest commit

 

History

History
68 lines (48 loc) · 2.42 KB

healthcare_service.html.markdown

File metadata and controls

68 lines (48 loc) · 2.42 KB
Raw
subcategory layout page_title description
Healthcare
azurerm
Azure Resource Manager: azurerm_healthcare_service
Get information about an existing Healthcare Service

Data Source: azurerm_healthcare_service

Use this data source to access information about an existing Healthcare Service

Example Usage

data "azurerm_healthcare_service" "example" {
  name                = "example-healthcare_service"
  resource_group_name = "example-resources"
  location            = "westus2"
}

output "healthcare_service_id" {
  value = data.azurerm_healthcare_service.example.id
}

Argument Reference

  • name - Specifies the name of the Healthcare Service.

  • resource_group_name - The name of the Resource Group in which the Healthcare Service exists.

Attributes Reference

The following attributes are exported:

  • location - The Azure Region where the Service is located.

~> Please Note: Not all locations support this resource. Some are West US 2, North Central US, and UK West.

  • kind - The type of the service.
  • authentication_configuration - An authentication_configuration block as defined below.
  • cosmosdb_throughput - The provisioned throughput for the backing database.
  • cosmosdb_key_vault_key_versionless_id - The versionless Key Vault Key ID for CMK encryption of the backing database.
  • cors_configuration - A cors_configuration block as defined below.
  • tags - A mapping of tags to assign to the resource.

An authentication_configuration exports the following:

  • authority - The Azure Active Directory (tenant) that serves as the authentication authority to access the service.
  • audience - The intended audience to receive authentication tokens for the service.
  • smart_proxy_enabled - Is the 'SMART on FHIR' option for mobile and web implementations enabled?

A cors_configuration block exports the following:

  • allowed_origins - The set of origins to be allowed via CORS.
  • allowed_headers - The set of headers to be allowed via CORS.
  • allowed_methods - The methods to be allowed via CORS.
  • max_age_in_seconds - The max age to be allowed via CORS.
  • allow_credentials - Are credentials are allowed via CORS?

Timeouts

The timeouts block allows you to specify timeouts for certain actions:

  • read - (Defaults to 5 minutes) Used when retrieving the Healthcare Service.