Table: azure_healthcare_service - Query Azure Healthcare Services using SQL
Azure Healthcare Services is a service within Microsoft Azure that allows users to manage and monitor health data in the cloud. It provides a centralized way to set up and manage healthcare services, including data protection, access control, and compliance features. Azure Healthcare Services helps users stay informed about the health and performance of their healthcare services and take appropriate actions when predefined conditions are met.
Table Usage Guide
The azure_healthcare_service
table provides insights into Healthcare Services within Microsoft Azure. As a healthcare data analyst, explore service-specific details through this table, including data protection measures, access control settings, and compliance features. Utilize it to uncover information about services, such as those with potential security risks, the access control settings of each service, and the compliance status of each service.
Examples
Basic info
Explore the characteristics and settings of your Azure Healthcare Services. This query can be useful for understanding the configuration and type of each service, which is essential for effective management and utilization of these services.
select name, id, kind, type, allow_credentials, audience, authorityfrom azure_healthcare_service;
select name, id, kind, type, allow_credentials, audience, authorityfrom azure_healthcare_service;
List healthcare services of fhir-R4 kind
Determine the areas in which specific healthcare services of 'fhir-R4' kind are utilized within the Azure platform. This can be helpful in assessing the usage and distribution of this particular type of service.
select name, id, type, kindfrom azure_healthcare_servicewhere kind = 'fhir-R4';
select name, id, type, kindfrom azure_healthcare_servicewhere kind = 'fhir-R4';
List private endpoint connection details for healthcare service
Gain insights into the private connection details of your healthcare service. This query is useful for understanding the connection's state and type, which can assist in troubleshooting or optimizing your service's network configuration.
select name, id, p ->> 'PrivateEndpointConnectionId' as private_endpoint_connection_id, p ->> 'ProvisioningState' as private_endpoint_provisioning_state, p ->> 'PrivateEndpointConnectionName' as private_endpoint_connection_name, p ->> 'PrivateEndpointConnectionType' as private_endpoint_connection_typefrom azure_healthcare_service, jsonb_array_elements(private_endpoint_connections) as p;
select name, s.id, json_extract(p.value, '$.PrivateEndpointConnectionId') as private_endpoint_connection_id, json_extract(p.value, '$.ProvisioningState') as private_endpoint_provisioning_state, json_extract(p.value, '$.PrivateEndpointConnectionName') as private_endpoint_connection_name, json_extract(p.value, '$.PrivateEndpointConnectionType') as private_endpoint_connection_typefrom azure_healthcare_service, json_each(private_endpoint_connections) as p;
List diagnostic settings for healthcare service
Explore the diagnostic settings of your healthcare service to gain insights into its configuration and performance. This can be beneficial for identifying potential issues or areas for improvement in your service's setup.
select name, id, d ->> 'id' as diagnostic_setting_id, d ->> 'name' as diagnostic_setting_name, d ->> 'type' as diagnostic_setting_type, d ->> 'properties' as diagnostic_setting_propertiesfrom azure_healthcare_service, jsonb_array_elements(diagnostic_settings) as d;
select name, s.id, json_extract(d.value, '$.id') as diagnostic_setting_id, json_extract(d.value, '$.name') as diagnostic_setting_name, json_extract(d.value, '$.type') as diagnostic_setting_type, json_extract(d.value, '$.properties') as diagnostic_setting_propertiesfrom azure_healthcare_service as s, json_each(diagnostic_settings) as d;
List Cosmos DB configuration settings
Gain insights into the configuration settings of your Azure Cosmos DB within the healthcare service. This analysis can help optimize the database performance and security by understanding key vault key URI and offer throughput details.
select name, id, cosmos_db_configuration ->> 'keyVaultKeyUri' as key_vault_key_uri, cosmos_db_configuration -> 'offerThroughput' as offer_throughputfrom azure_healthcare_service;
select name, id, json_extract(cosmos_db_configuration, '$.keyVaultKeyUri') as key_vault_key_uri, json_extract(cosmos_db_configuration, '$.offerThroughput') as offer_throughputfrom azure_healthcare_service;
Control examples
Schema for azure_healthcare_service
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
access_policies | jsonb | The access policies of the healthcare service. | |
akas | jsonb | Array of globally unique identifier strings (also known as) for the resource. | |
allow_credentials | boolean | If credentials are allowed via CORS. | |
audience | text | The audience url for the service. | |
authority | text | The authority url for the service. | |
cloud_environment | text | The Azure Cloud Environment. | |
cosmos_db_configuration | jsonb | The settings for the Cosmos DB database backing the service. | |
diagnostic_settings | jsonb | A list of active diagnostic settings for the healthcare serive. | |
etag | text | An etag associated with the resource, used for optimistic concurrency when editing it. | |
headers | jsonb | The headers to be allowed via CORS. | |
id | text | The resource identifier. | |
kind | text | The kind of the service. Possible values include: 'Fhir', 'FhirStu3', 'FhirR4'. | |
location | text | The resource location. | |
max_age | bigint | The max age to be allowed via CORS. | |
methods | jsonb | The methods to be allowed via CORS. | |
name | text | = | The resource name. |
origins | jsonb | The origins to be allowed via CORS. | |
private_endpoint_connections | jsonb | List of private endpoint connections for healthcare service. | |
provisioning_state | text | The provisioning state of the healthcare service resource. | |
region | text | The Azure region/location in which the resource is located. | |
resource_group | text | = | The resource group which holds this resource. |
smart_proxy_enabled | boolean | If the SMART on FHIR proxy is enabled. | |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
subscription_id | text | =, !=, ~~, ~~*, !~~, !~~* | The Azure Subscription ID in which the resource is located. |
tags | jsonb | A map of tags for the resource. | |
title | text | Title of the resource. | |
type | text | The resource type. |
Export
This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.
You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh
script:
/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- azure
You can pass the configuration to the command with the --config
argument:
steampipe_export_azure --config '<your_config>' azure_healthcare_service