Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi
google-native.healthcare/v1beta1.getFhirStore
Explore with Pulumi AI
Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi
Gets the configuration of the specified FHIR store.
Using getFhirStore
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getFhirStore(args: GetFhirStoreArgs, opts?: InvokeOptions): Promise<GetFhirStoreResult>
function getFhirStoreOutput(args: GetFhirStoreOutputArgs, opts?: InvokeOptions): Output<GetFhirStoreResult>def get_fhir_store(dataset_id: Optional[str] = None,
                   fhir_store_id: Optional[str] = None,
                   location: Optional[str] = None,
                   project: Optional[str] = None,
                   opts: Optional[InvokeOptions] = None) -> GetFhirStoreResult
def get_fhir_store_output(dataset_id: Optional[pulumi.Input[str]] = None,
                   fhir_store_id: Optional[pulumi.Input[str]] = None,
                   location: Optional[pulumi.Input[str]] = None,
                   project: Optional[pulumi.Input[str]] = None,
                   opts: Optional[InvokeOptions] = None) -> Output[GetFhirStoreResult]func LookupFhirStore(ctx *Context, args *LookupFhirStoreArgs, opts ...InvokeOption) (*LookupFhirStoreResult, error)
func LookupFhirStoreOutput(ctx *Context, args *LookupFhirStoreOutputArgs, opts ...InvokeOption) LookupFhirStoreResultOutput> Note: This function is named LookupFhirStore in the Go SDK.
public static class GetFhirStore 
{
    public static Task<GetFhirStoreResult> InvokeAsync(GetFhirStoreArgs args, InvokeOptions? opts = null)
    public static Output<GetFhirStoreResult> Invoke(GetFhirStoreInvokeArgs args, InvokeOptions? opts = null)
}public static CompletableFuture<GetFhirStoreResult> getFhirStore(GetFhirStoreArgs args, InvokeOptions options)
public static Output<GetFhirStoreResult> getFhirStore(GetFhirStoreArgs args, InvokeOptions options)
fn::invoke:
  function: google-native:healthcare/v1beta1:getFhirStore
  arguments:
    # arguments dictionaryThe following arguments are supported:
- DatasetId string
- FhirStore stringId 
- Location string
- Project string
- DatasetId string
- FhirStore stringId 
- Location string
- Project string
- datasetId String
- fhirStore StringId 
- location String
- project String
- datasetId string
- fhirStore stringId 
- location string
- project string
- dataset_id str
- fhir_store_ strid 
- location str
- project str
- datasetId String
- fhirStore StringId 
- location String
- project String
getFhirStore Result
The following output properties are available:
- ComplexData stringType Reference Parsing 
- Enable parsing of references within complex FHIR data types such as Extensions. If this value is set to ENABLED, then features like referential integrity and Bundle reference rewriting apply to all references. If this flag has not been specified the behavior of the FHIR store will not change, references in complex data types will not be parsed. New stores will have this value set to ENABLED after a notification period. Warning: turning on this flag causes processing existing resources to fail if they contain references to non-existent resources.
- ConsentConfig Pulumi.Google Native. Healthcare. V1Beta1. Outputs. Consent Config Response 
- Optional. Specifies whether this store has consent enforcement. Not available for DSTU2 FHIR version due to absence of Consent resources.
- DefaultSearch boolHandling Strict 
- If true, overrides the default search behavior for this FHIR store to handling=strictwhich returns an error for unrecognized search parameters. If false, uses the FHIR specification defaulthandling=lenientwhich ignores unrecognized search parameters. The handling can always be changed from the default on an individual API call by setting the HTTP headerPrefer: handling=strictorPrefer: handling=lenient.
- DisableReferential boolIntegrity 
- Immutable. Whether to disable referential integrity in this FHIR store. This field is immutable after FHIR store creation. The default value is false, meaning that the API enforces referential integrity and fails the requests that result in inconsistent state in the FHIR store. When this field is set to true, the API skips referential integrity checks. Consequently, operations that rely on references, such as GetPatientEverything, do not return all the results if broken references exist.
- DisableResource boolVersioning 
- Immutable. Whether to disable resource versioning for this FHIR store. This field can not be changed after the creation of FHIR store. If set to false, which is the default behavior, all write operations cause historical versions to be recorded automatically. The historical versions can be fetched through the history APIs, but cannot be updated. If set to true, no historical versions are kept. The server sends errors for attempts to read the historical versions.
- EnableUpdate boolCreate 
- Whether this FHIR store has the updateCreate capability. This determines if the client can use an Update operation to create a new resource with a client-specified ID. If false, all IDs are server-assigned through the Create operation and attempts to update a non-existent resource return errors. It is strongly advised not to include or encode any sensitive data such as patient identifiers in client-specified resource IDs. Those IDs are part of the FHIR resource path recorded in Cloud audit logs and Pub/Sub notifications. Those IDs can also be contained in reference fields within other resources.
- Labels Dictionary<string, string>
- User-supplied key-value pairs used to organize FHIR stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: \p{Ll}\p{Lo}{0,62} Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: [\p{Ll}\p{Lo}\p{N}_-]{0,63} No more than 64 labels can be associated with a given store.
- Name string
- Resource name of the FHIR store, of the form projects/{project_id}/datasets/{dataset_id}/fhirStores/{fhir_store_id}.
- NotificationConfig Pulumi.Google Native. Healthcare. V1Beta1. Outputs. Notification Config Response 
- Deprecated. Use notification_configsinstead. If non-empty, publish all resource modifications of this FHIR store to this destination. The Pub/Sub message attributes contain a map with a string describing the action that has triggered the notification. For example, "action":"CreateResource".
- NotificationConfigs List<Pulumi.Google Native. Healthcare. V1Beta1. Outputs. Fhir Notification Config Response> 
- Specifies where and whether to send notifications upon changes to a Fhir store.
- SearchConfig Pulumi.Google Native. Healthcare. V1Beta1. Outputs. Search Config Response 
- Configuration for how FHIR resources can be searched.
- StreamConfigs List<Pulumi.Google Native. Healthcare. V1Beta1. Outputs. Stream Config Response> 
- A list of streaming configs that configure the destinations of streaming export for every resource mutation in this FHIR store. Each store is allowed to have up to 10 streaming configs. After a new config is added, the next resource mutation is streamed to the new location in addition to the existing ones. When a location is removed from the list, the server stops streaming to that location. Before adding a new config, you must add the required bigquery.dataEditorrole to your project's Cloud Healthcare Service Agent service account. Some lag (typically on the order of dozens of seconds) is expected before the results show up in the streaming destination.
- ValidationConfig Pulumi.Google Native. Healthcare. V1Beta1. Outputs. Validation Config Response 
- Configuration for how to validate incoming FHIR resources against configured profiles.
- Version string
- Immutable. The FHIR specification version that this FHIR store supports natively. This field is immutable after store creation. Requests are rejected if they contain FHIR resources of a different version. Version is required for every FHIR store.
- ComplexData stringType Reference Parsing 
- Enable parsing of references within complex FHIR data types such as Extensions. If this value is set to ENABLED, then features like referential integrity and Bundle reference rewriting apply to all references. If this flag has not been specified the behavior of the FHIR store will not change, references in complex data types will not be parsed. New stores will have this value set to ENABLED after a notification period. Warning: turning on this flag causes processing existing resources to fail if they contain references to non-existent resources.
- ConsentConfig ConsentConfig Response 
- Optional. Specifies whether this store has consent enforcement. Not available for DSTU2 FHIR version due to absence of Consent resources.
- DefaultSearch boolHandling Strict 
- If true, overrides the default search behavior for this FHIR store to handling=strictwhich returns an error for unrecognized search parameters. If false, uses the FHIR specification defaulthandling=lenientwhich ignores unrecognized search parameters. The handling can always be changed from the default on an individual API call by setting the HTTP headerPrefer: handling=strictorPrefer: handling=lenient.
- DisableReferential boolIntegrity 
- Immutable. Whether to disable referential integrity in this FHIR store. This field is immutable after FHIR store creation. The default value is false, meaning that the API enforces referential integrity and fails the requests that result in inconsistent state in the FHIR store. When this field is set to true, the API skips referential integrity checks. Consequently, operations that rely on references, such as GetPatientEverything, do not return all the results if broken references exist.
- DisableResource boolVersioning 
- Immutable. Whether to disable resource versioning for this FHIR store. This field can not be changed after the creation of FHIR store. If set to false, which is the default behavior, all write operations cause historical versions to be recorded automatically. The historical versions can be fetched through the history APIs, but cannot be updated. If set to true, no historical versions are kept. The server sends errors for attempts to read the historical versions.
- EnableUpdate boolCreate 
- Whether this FHIR store has the updateCreate capability. This determines if the client can use an Update operation to create a new resource with a client-specified ID. If false, all IDs are server-assigned through the Create operation and attempts to update a non-existent resource return errors. It is strongly advised not to include or encode any sensitive data such as patient identifiers in client-specified resource IDs. Those IDs are part of the FHIR resource path recorded in Cloud audit logs and Pub/Sub notifications. Those IDs can also be contained in reference fields within other resources.
- Labels map[string]string
- User-supplied key-value pairs used to organize FHIR stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: \p{Ll}\p{Lo}{0,62} Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: [\p{Ll}\p{Lo}\p{N}_-]{0,63} No more than 64 labels can be associated with a given store.
- Name string
- Resource name of the FHIR store, of the form projects/{project_id}/datasets/{dataset_id}/fhirStores/{fhir_store_id}.
- NotificationConfig NotificationConfig Response 
- Deprecated. Use notification_configsinstead. If non-empty, publish all resource modifications of this FHIR store to this destination. The Pub/Sub message attributes contain a map with a string describing the action that has triggered the notification. For example, "action":"CreateResource".
- NotificationConfigs []FhirNotification Config Response 
- Specifies where and whether to send notifications upon changes to a Fhir store.
- SearchConfig SearchConfig Response 
- Configuration for how FHIR resources can be searched.
- StreamConfigs []StreamConfig Response 
- A list of streaming configs that configure the destinations of streaming export for every resource mutation in this FHIR store. Each store is allowed to have up to 10 streaming configs. After a new config is added, the next resource mutation is streamed to the new location in addition to the existing ones. When a location is removed from the list, the server stops streaming to that location. Before adding a new config, you must add the required bigquery.dataEditorrole to your project's Cloud Healthcare Service Agent service account. Some lag (typically on the order of dozens of seconds) is expected before the results show up in the streaming destination.
- ValidationConfig ValidationConfig Response 
- Configuration for how to validate incoming FHIR resources against configured profiles.
- Version string
- Immutable. The FHIR specification version that this FHIR store supports natively. This field is immutable after store creation. Requests are rejected if they contain FHIR resources of a different version. Version is required for every FHIR store.
- complexData StringType Reference Parsing 
- Enable parsing of references within complex FHIR data types such as Extensions. If this value is set to ENABLED, then features like referential integrity and Bundle reference rewriting apply to all references. If this flag has not been specified the behavior of the FHIR store will not change, references in complex data types will not be parsed. New stores will have this value set to ENABLED after a notification period. Warning: turning on this flag causes processing existing resources to fail if they contain references to non-existent resources.
- consentConfig ConsentConfig Response 
- Optional. Specifies whether this store has consent enforcement. Not available for DSTU2 FHIR version due to absence of Consent resources.
- defaultSearch BooleanHandling Strict 
- If true, overrides the default search behavior for this FHIR store to handling=strictwhich returns an error for unrecognized search parameters. If false, uses the FHIR specification defaulthandling=lenientwhich ignores unrecognized search parameters. The handling can always be changed from the default on an individual API call by setting the HTTP headerPrefer: handling=strictorPrefer: handling=lenient.
- disableReferential BooleanIntegrity 
- Immutable. Whether to disable referential integrity in this FHIR store. This field is immutable after FHIR store creation. The default value is false, meaning that the API enforces referential integrity and fails the requests that result in inconsistent state in the FHIR store. When this field is set to true, the API skips referential integrity checks. Consequently, operations that rely on references, such as GetPatientEverything, do not return all the results if broken references exist.
- disableResource BooleanVersioning 
- Immutable. Whether to disable resource versioning for this FHIR store. This field can not be changed after the creation of FHIR store. If set to false, which is the default behavior, all write operations cause historical versions to be recorded automatically. The historical versions can be fetched through the history APIs, but cannot be updated. If set to true, no historical versions are kept. The server sends errors for attempts to read the historical versions.
- enableUpdate BooleanCreate 
- Whether this FHIR store has the updateCreate capability. This determines if the client can use an Update operation to create a new resource with a client-specified ID. If false, all IDs are server-assigned through the Create operation and attempts to update a non-existent resource return errors. It is strongly advised not to include or encode any sensitive data such as patient identifiers in client-specified resource IDs. Those IDs are part of the FHIR resource path recorded in Cloud audit logs and Pub/Sub notifications. Those IDs can also be contained in reference fields within other resources.
- labels Map<String,String>
- User-supplied key-value pairs used to organize FHIR stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: \p{Ll}\p{Lo}{0,62} Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: [\p{Ll}\p{Lo}\p{N}_-]{0,63} No more than 64 labels can be associated with a given store.
- name String
- Resource name of the FHIR store, of the form projects/{project_id}/datasets/{dataset_id}/fhirStores/{fhir_store_id}.
- notificationConfig NotificationConfig Response 
- Deprecated. Use notification_configsinstead. If non-empty, publish all resource modifications of this FHIR store to this destination. The Pub/Sub message attributes contain a map with a string describing the action that has triggered the notification. For example, "action":"CreateResource".
- notificationConfigs List<FhirNotification Config Response> 
- Specifies where and whether to send notifications upon changes to a Fhir store.
- searchConfig SearchConfig Response 
- Configuration for how FHIR resources can be searched.
- streamConfigs List<StreamConfig Response> 
- A list of streaming configs that configure the destinations of streaming export for every resource mutation in this FHIR store. Each store is allowed to have up to 10 streaming configs. After a new config is added, the next resource mutation is streamed to the new location in addition to the existing ones. When a location is removed from the list, the server stops streaming to that location. Before adding a new config, you must add the required bigquery.dataEditorrole to your project's Cloud Healthcare Service Agent service account. Some lag (typically on the order of dozens of seconds) is expected before the results show up in the streaming destination.
- validationConfig ValidationConfig Response 
- Configuration for how to validate incoming FHIR resources against configured profiles.
- version String
- Immutable. The FHIR specification version that this FHIR store supports natively. This field is immutable after store creation. Requests are rejected if they contain FHIR resources of a different version. Version is required for every FHIR store.
- complexData stringType Reference Parsing 
- Enable parsing of references within complex FHIR data types such as Extensions. If this value is set to ENABLED, then features like referential integrity and Bundle reference rewriting apply to all references. If this flag has not been specified the behavior of the FHIR store will not change, references in complex data types will not be parsed. New stores will have this value set to ENABLED after a notification period. Warning: turning on this flag causes processing existing resources to fail if they contain references to non-existent resources.
- consentConfig ConsentConfig Response 
- Optional. Specifies whether this store has consent enforcement. Not available for DSTU2 FHIR version due to absence of Consent resources.
- defaultSearch booleanHandling Strict 
- If true, overrides the default search behavior for this FHIR store to handling=strictwhich returns an error for unrecognized search parameters. If false, uses the FHIR specification defaulthandling=lenientwhich ignores unrecognized search parameters. The handling can always be changed from the default on an individual API call by setting the HTTP headerPrefer: handling=strictorPrefer: handling=lenient.
- disableReferential booleanIntegrity 
- Immutable. Whether to disable referential integrity in this FHIR store. This field is immutable after FHIR store creation. The default value is false, meaning that the API enforces referential integrity and fails the requests that result in inconsistent state in the FHIR store. When this field is set to true, the API skips referential integrity checks. Consequently, operations that rely on references, such as GetPatientEverything, do not return all the results if broken references exist.
- disableResource booleanVersioning 
- Immutable. Whether to disable resource versioning for this FHIR store. This field can not be changed after the creation of FHIR store. If set to false, which is the default behavior, all write operations cause historical versions to be recorded automatically. The historical versions can be fetched through the history APIs, but cannot be updated. If set to true, no historical versions are kept. The server sends errors for attempts to read the historical versions.
- enableUpdate booleanCreate 
- Whether this FHIR store has the updateCreate capability. This determines if the client can use an Update operation to create a new resource with a client-specified ID. If false, all IDs are server-assigned through the Create operation and attempts to update a non-existent resource return errors. It is strongly advised not to include or encode any sensitive data such as patient identifiers in client-specified resource IDs. Those IDs are part of the FHIR resource path recorded in Cloud audit logs and Pub/Sub notifications. Those IDs can also be contained in reference fields within other resources.
- labels {[key: string]: string}
- User-supplied key-value pairs used to organize FHIR stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: \p{Ll}\p{Lo}{0,62} Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: [\p{Ll}\p{Lo}\p{N}_-]{0,63} No more than 64 labels can be associated with a given store.
- name string
- Resource name of the FHIR store, of the form projects/{project_id}/datasets/{dataset_id}/fhirStores/{fhir_store_id}.
- notificationConfig NotificationConfig Response 
- Deprecated. Use notification_configsinstead. If non-empty, publish all resource modifications of this FHIR store to this destination. The Pub/Sub message attributes contain a map with a string describing the action that has triggered the notification. For example, "action":"CreateResource".
- notificationConfigs FhirNotification Config Response[] 
- Specifies where and whether to send notifications upon changes to a Fhir store.
- searchConfig SearchConfig Response 
- Configuration for how FHIR resources can be searched.
- streamConfigs StreamConfig Response[] 
- A list of streaming configs that configure the destinations of streaming export for every resource mutation in this FHIR store. Each store is allowed to have up to 10 streaming configs. After a new config is added, the next resource mutation is streamed to the new location in addition to the existing ones. When a location is removed from the list, the server stops streaming to that location. Before adding a new config, you must add the required bigquery.dataEditorrole to your project's Cloud Healthcare Service Agent service account. Some lag (typically on the order of dozens of seconds) is expected before the results show up in the streaming destination.
- validationConfig ValidationConfig Response 
- Configuration for how to validate incoming FHIR resources against configured profiles.
- version string
- Immutable. The FHIR specification version that this FHIR store supports natively. This field is immutable after store creation. Requests are rejected if they contain FHIR resources of a different version. Version is required for every FHIR store.
- complex_data_ strtype_ reference_ parsing 
- Enable parsing of references within complex FHIR data types such as Extensions. If this value is set to ENABLED, then features like referential integrity and Bundle reference rewriting apply to all references. If this flag has not been specified the behavior of the FHIR store will not change, references in complex data types will not be parsed. New stores will have this value set to ENABLED after a notification period. Warning: turning on this flag causes processing existing resources to fail if they contain references to non-existent resources.
- consent_config ConsentConfig Response 
- Optional. Specifies whether this store has consent enforcement. Not available for DSTU2 FHIR version due to absence of Consent resources.
- default_search_ boolhandling_ strict 
- If true, overrides the default search behavior for this FHIR store to handling=strictwhich returns an error for unrecognized search parameters. If false, uses the FHIR specification defaulthandling=lenientwhich ignores unrecognized search parameters. The handling can always be changed from the default on an individual API call by setting the HTTP headerPrefer: handling=strictorPrefer: handling=lenient.
- disable_referential_ boolintegrity 
- Immutable. Whether to disable referential integrity in this FHIR store. This field is immutable after FHIR store creation. The default value is false, meaning that the API enforces referential integrity and fails the requests that result in inconsistent state in the FHIR store. When this field is set to true, the API skips referential integrity checks. Consequently, operations that rely on references, such as GetPatientEverything, do not return all the results if broken references exist.
- disable_resource_ boolversioning 
- Immutable. Whether to disable resource versioning for this FHIR store. This field can not be changed after the creation of FHIR store. If set to false, which is the default behavior, all write operations cause historical versions to be recorded automatically. The historical versions can be fetched through the history APIs, but cannot be updated. If set to true, no historical versions are kept. The server sends errors for attempts to read the historical versions.
- enable_update_ boolcreate 
- Whether this FHIR store has the updateCreate capability. This determines if the client can use an Update operation to create a new resource with a client-specified ID. If false, all IDs are server-assigned through the Create operation and attempts to update a non-existent resource return errors. It is strongly advised not to include or encode any sensitive data such as patient identifiers in client-specified resource IDs. Those IDs are part of the FHIR resource path recorded in Cloud audit logs and Pub/Sub notifications. Those IDs can also be contained in reference fields within other resources.
- labels Mapping[str, str]
- User-supplied key-value pairs used to organize FHIR stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: \p{Ll}\p{Lo}{0,62} Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: [\p{Ll}\p{Lo}\p{N}_-]{0,63} No more than 64 labels can be associated with a given store.
- name str
- Resource name of the FHIR store, of the form projects/{project_id}/datasets/{dataset_id}/fhirStores/{fhir_store_id}.
- notification_config NotificationConfig Response 
- Deprecated. Use notification_configsinstead. If non-empty, publish all resource modifications of this FHIR store to this destination. The Pub/Sub message attributes contain a map with a string describing the action that has triggered the notification. For example, "action":"CreateResource".
- notification_configs Sequence[FhirNotification Config Response] 
- Specifies where and whether to send notifications upon changes to a Fhir store.
- search_config SearchConfig Response 
- Configuration for how FHIR resources can be searched.
- stream_configs Sequence[StreamConfig Response] 
- A list of streaming configs that configure the destinations of streaming export for every resource mutation in this FHIR store. Each store is allowed to have up to 10 streaming configs. After a new config is added, the next resource mutation is streamed to the new location in addition to the existing ones. When a location is removed from the list, the server stops streaming to that location. Before adding a new config, you must add the required bigquery.dataEditorrole to your project's Cloud Healthcare Service Agent service account. Some lag (typically on the order of dozens of seconds) is expected before the results show up in the streaming destination.
- validation_config ValidationConfig Response 
- Configuration for how to validate incoming FHIR resources against configured profiles.
- version str
- Immutable. The FHIR specification version that this FHIR store supports natively. This field is immutable after store creation. Requests are rejected if they contain FHIR resources of a different version. Version is required for every FHIR store.
- complexData StringType Reference Parsing 
- Enable parsing of references within complex FHIR data types such as Extensions. If this value is set to ENABLED, then features like referential integrity and Bundle reference rewriting apply to all references. If this flag has not been specified the behavior of the FHIR store will not change, references in complex data types will not be parsed. New stores will have this value set to ENABLED after a notification period. Warning: turning on this flag causes processing existing resources to fail if they contain references to non-existent resources.
- consentConfig Property Map
- Optional. Specifies whether this store has consent enforcement. Not available for DSTU2 FHIR version due to absence of Consent resources.
- defaultSearch BooleanHandling Strict 
- If true, overrides the default search behavior for this FHIR store to handling=strictwhich returns an error for unrecognized search parameters. If false, uses the FHIR specification defaulthandling=lenientwhich ignores unrecognized search parameters. The handling can always be changed from the default on an individual API call by setting the HTTP headerPrefer: handling=strictorPrefer: handling=lenient.
- disableReferential BooleanIntegrity 
- Immutable. Whether to disable referential integrity in this FHIR store. This field is immutable after FHIR store creation. The default value is false, meaning that the API enforces referential integrity and fails the requests that result in inconsistent state in the FHIR store. When this field is set to true, the API skips referential integrity checks. Consequently, operations that rely on references, such as GetPatientEverything, do not return all the results if broken references exist.
- disableResource BooleanVersioning 
- Immutable. Whether to disable resource versioning for this FHIR store. This field can not be changed after the creation of FHIR store. If set to false, which is the default behavior, all write operations cause historical versions to be recorded automatically. The historical versions can be fetched through the history APIs, but cannot be updated. If set to true, no historical versions are kept. The server sends errors for attempts to read the historical versions.
- enableUpdate BooleanCreate 
- Whether this FHIR store has the updateCreate capability. This determines if the client can use an Update operation to create a new resource with a client-specified ID. If false, all IDs are server-assigned through the Create operation and attempts to update a non-existent resource return errors. It is strongly advised not to include or encode any sensitive data such as patient identifiers in client-specified resource IDs. Those IDs are part of the FHIR resource path recorded in Cloud audit logs and Pub/Sub notifications. Those IDs can also be contained in reference fields within other resources.
- labels Map<String>
- User-supplied key-value pairs used to organize FHIR stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: \p{Ll}\p{Lo}{0,62} Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: [\p{Ll}\p{Lo}\p{N}_-]{0,63} No more than 64 labels can be associated with a given store.
- name String
- Resource name of the FHIR store, of the form projects/{project_id}/datasets/{dataset_id}/fhirStores/{fhir_store_id}.
- notificationConfig Property Map
- Deprecated. Use notification_configsinstead. If non-empty, publish all resource modifications of this FHIR store to this destination. The Pub/Sub message attributes contain a map with a string describing the action that has triggered the notification. For example, "action":"CreateResource".
- notificationConfigs List<Property Map>
- Specifies where and whether to send notifications upon changes to a Fhir store.
- searchConfig Property Map
- Configuration for how FHIR resources can be searched.
- streamConfigs List<Property Map>
- A list of streaming configs that configure the destinations of streaming export for every resource mutation in this FHIR store. Each store is allowed to have up to 10 streaming configs. After a new config is added, the next resource mutation is streamed to the new location in addition to the existing ones. When a location is removed from the list, the server stops streaming to that location. Before adding a new config, you must add the required bigquery.dataEditorrole to your project's Cloud Healthcare Service Agent service account. Some lag (typically on the order of dozens of seconds) is expected before the results show up in the streaming destination.
- validationConfig Property Map
- Configuration for how to validate incoming FHIR resources against configured profiles.
- version String
- Immutable. The FHIR specification version that this FHIR store supports natively. This field is immutable after store creation. Requests are rejected if they contain FHIR resources of a different version. Version is required for every FHIR store.
Supporting Types
AccessDeterminationLogConfigResponse    
- LogLevel string
- Optional. Controls the amount of detail to include as part of the audit logs.
- LogLevel string
- Optional. Controls the amount of detail to include as part of the audit logs.
- logLevel String
- Optional. Controls the amount of detail to include as part of the audit logs.
- logLevel string
- Optional. Controls the amount of detail to include as part of the audit logs.
- log_level str
- Optional. Controls the amount of detail to include as part of the audit logs.
- logLevel String
- Optional. Controls the amount of detail to include as part of the audit logs.
ActionResponse 
- CleanImage Pulumi.Tag Google Native. Healthcare. V1Beta1. Inputs. Image Config Response 
- Inspect image and transform sensitive burnt-in text. Doesn't apply to elements nested in a sequence, which revert to Keep. Supported tags: PixelData
- CleanText Pulumi.Tag Google Native. Healthcare. V1Beta1. Inputs. Clean Text Tag Response 
- Inspect text and transform sensitive text. Configurable via TextConfig. Supported Value Representations: AE, LO, LT, PN, SH, ST, UC, UT, DA, DT, AS
- DeleteTag Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Delete Tag Response 
- Delete tag.
- KeepTag Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Keep Tag Response 
- Keep tag unchanged.
- Queries List<string>
- Select all tags with the listed tag IDs, names, or Value Representations (VRs). Examples: ID: "00100010" Keyword: "PatientName" VR: "PN"
- RecurseTag Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Recurse Tag Response 
- Recursively apply DICOM de-id to tags nested in a sequence. Supported [Value Representation] (http://dicom.nema.org/medical/dicom/2018e/output/chtml/part05/sect_6.2.html#table_6.2-1): SQ
- RegenUid Pulumi.Tag Google Native. Healthcare. V1Beta1. Inputs. Regen Uid Tag Response 
- Replace UID with a new generated UID. Supported [Value Representation] (http://dicom.nema.org/medical/dicom/2018e/output/chtml/part05/sect_6.2.html#table_6.2-1): UI
- RemoveTag Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Remove Tag Response 
- Replace with empty tag.
- ResetTag Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Reset Tag Response 
- Reset tag to a placeholder value.
- CleanImage ImageTag Config Response 
- Inspect image and transform sensitive burnt-in text. Doesn't apply to elements nested in a sequence, which revert to Keep. Supported tags: PixelData
- CleanText CleanTag Text Tag Response 
- Inspect text and transform sensitive text. Configurable via TextConfig. Supported Value Representations: AE, LO, LT, PN, SH, ST, UC, UT, DA, DT, AS
- DeleteTag DeleteTag Response 
- Delete tag.
- KeepTag KeepTag Response 
- Keep tag unchanged.
- Queries []string
- Select all tags with the listed tag IDs, names, or Value Representations (VRs). Examples: ID: "00100010" Keyword: "PatientName" VR: "PN"
- RecurseTag RecurseTag Response 
- Recursively apply DICOM de-id to tags nested in a sequence. Supported [Value Representation] (http://dicom.nema.org/medical/dicom/2018e/output/chtml/part05/sect_6.2.html#table_6.2-1): SQ
- RegenUid RegenTag Uid Tag Response 
- Replace UID with a new generated UID. Supported [Value Representation] (http://dicom.nema.org/medical/dicom/2018e/output/chtml/part05/sect_6.2.html#table_6.2-1): UI
- RemoveTag RemoveTag Response 
- Replace with empty tag.
- ResetTag ResetTag Response 
- Reset tag to a placeholder value.
- cleanImage ImageTag Config Response 
- Inspect image and transform sensitive burnt-in text. Doesn't apply to elements nested in a sequence, which revert to Keep. Supported tags: PixelData
- cleanText CleanTag Text Tag Response 
- Inspect text and transform sensitive text. Configurable via TextConfig. Supported Value Representations: AE, LO, LT, PN, SH, ST, UC, UT, DA, DT, AS
- deleteTag DeleteTag Response 
- Delete tag.
- keepTag KeepTag Response 
- Keep tag unchanged.
- queries List<String>
- Select all tags with the listed tag IDs, names, or Value Representations (VRs). Examples: ID: "00100010" Keyword: "PatientName" VR: "PN"
- recurseTag RecurseTag Response 
- Recursively apply DICOM de-id to tags nested in a sequence. Supported [Value Representation] (http://dicom.nema.org/medical/dicom/2018e/output/chtml/part05/sect_6.2.html#table_6.2-1): SQ
- regenUid RegenTag Uid Tag Response 
- Replace UID with a new generated UID. Supported [Value Representation] (http://dicom.nema.org/medical/dicom/2018e/output/chtml/part05/sect_6.2.html#table_6.2-1): UI
- removeTag RemoveTag Response 
- Replace with empty tag.
- resetTag ResetTag Response 
- Reset tag to a placeholder value.
- cleanImage ImageTag Config Response 
- Inspect image and transform sensitive burnt-in text. Doesn't apply to elements nested in a sequence, which revert to Keep. Supported tags: PixelData
- cleanText CleanTag Text Tag Response 
- Inspect text and transform sensitive text. Configurable via TextConfig. Supported Value Representations: AE, LO, LT, PN, SH, ST, UC, UT, DA, DT, AS
- deleteTag DeleteTag Response 
- Delete tag.
- keepTag KeepTag Response 
- Keep tag unchanged.
- queries string[]
- Select all tags with the listed tag IDs, names, or Value Representations (VRs). Examples: ID: "00100010" Keyword: "PatientName" VR: "PN"
- recurseTag RecurseTag Response 
- Recursively apply DICOM de-id to tags nested in a sequence. Supported [Value Representation] (http://dicom.nema.org/medical/dicom/2018e/output/chtml/part05/sect_6.2.html#table_6.2-1): SQ
- regenUid RegenTag Uid Tag Response 
- Replace UID with a new generated UID. Supported [Value Representation] (http://dicom.nema.org/medical/dicom/2018e/output/chtml/part05/sect_6.2.html#table_6.2-1): UI
- removeTag RemoveTag Response 
- Replace with empty tag.
- resetTag ResetTag Response 
- Reset tag to a placeholder value.
- clean_image_ Imagetag Config Response 
- Inspect image and transform sensitive burnt-in text. Doesn't apply to elements nested in a sequence, which revert to Keep. Supported tags: PixelData
- clean_text_ Cleantag Text Tag Response 
- Inspect text and transform sensitive text. Configurable via TextConfig. Supported Value Representations: AE, LO, LT, PN, SH, ST, UC, UT, DA, DT, AS
- delete_tag DeleteTag Response 
- Delete tag.
- keep_tag KeepTag Response 
- Keep tag unchanged.
- queries Sequence[str]
- Select all tags with the listed tag IDs, names, or Value Representations (VRs). Examples: ID: "00100010" Keyword: "PatientName" VR: "PN"
- recurse_tag RecurseTag Response 
- Recursively apply DICOM de-id to tags nested in a sequence. Supported [Value Representation] (http://dicom.nema.org/medical/dicom/2018e/output/chtml/part05/sect_6.2.html#table_6.2-1): SQ
- regen_uid_ Regentag Uid Tag Response 
- Replace UID with a new generated UID. Supported [Value Representation] (http://dicom.nema.org/medical/dicom/2018e/output/chtml/part05/sect_6.2.html#table_6.2-1): UI
- remove_tag RemoveTag Response 
- Replace with empty tag.
- reset_tag ResetTag Response 
- Reset tag to a placeholder value.
- cleanImage Property MapTag 
- Inspect image and transform sensitive burnt-in text. Doesn't apply to elements nested in a sequence, which revert to Keep. Supported tags: PixelData
- cleanText Property MapTag 
- Inspect text and transform sensitive text. Configurable via TextConfig. Supported Value Representations: AE, LO, LT, PN, SH, ST, UC, UT, DA, DT, AS
- deleteTag Property Map
- Delete tag.
- keepTag Property Map
- Keep tag unchanged.
- queries List<String>
- Select all tags with the listed tag IDs, names, or Value Representations (VRs). Examples: ID: "00100010" Keyword: "PatientName" VR: "PN"
- recurseTag Property Map
- Recursively apply DICOM de-id to tags nested in a sequence. Supported [Value Representation] (http://dicom.nema.org/medical/dicom/2018e/output/chtml/part05/sect_6.2.html#table_6.2-1): SQ
- regenUid Property MapTag 
- Replace UID with a new generated UID. Supported [Value Representation] (http://dicom.nema.org/medical/dicom/2018e/output/chtml/part05/sect_6.2.html#table_6.2-1): UI
- removeTag Property Map
- Replace with empty tag.
- resetTag Property Map
- Reset tag to a placeholder value.
AnnotationConfigResponse  
- AnnotationStore stringName 
- The name of the annotation store, in the form projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/annotationStores/{annotation_store_id}). * The destination annotation store must be in the same project as the source data. De-identifying data across multiple projects is not supported. * The destination annotation store must exist when using DeidentifyDicomStore or DeidentifyFhirStore. DeidentifyDataset automatically creates the destination annotation store.
- StoreQuote bool
- If set to true, the sensitive texts are included in SensitiveTextAnnotation of Annotation.
- AnnotationStore stringName 
- The name of the annotation store, in the form projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/annotationStores/{annotation_store_id}). * The destination annotation store must be in the same project as the source data. De-identifying data across multiple projects is not supported. * The destination annotation store must exist when using DeidentifyDicomStore or DeidentifyFhirStore. DeidentifyDataset automatically creates the destination annotation store.
- StoreQuote bool
- If set to true, the sensitive texts are included in SensitiveTextAnnotation of Annotation.
- annotationStore StringName 
- The name of the annotation store, in the form projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/annotationStores/{annotation_store_id}). * The destination annotation store must be in the same project as the source data. De-identifying data across multiple projects is not supported. * The destination annotation store must exist when using DeidentifyDicomStore or DeidentifyFhirStore. DeidentifyDataset automatically creates the destination annotation store.
- storeQuote Boolean
- If set to true, the sensitive texts are included in SensitiveTextAnnotation of Annotation.
- annotationStore stringName 
- The name of the annotation store, in the form projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/annotationStores/{annotation_store_id}). * The destination annotation store must be in the same project as the source data. De-identifying data across multiple projects is not supported. * The destination annotation store must exist when using DeidentifyDicomStore or DeidentifyFhirStore. DeidentifyDataset automatically creates the destination annotation store.
- storeQuote boolean
- If set to true, the sensitive texts are included in SensitiveTextAnnotation of Annotation.
- annotation_store_ strname 
- The name of the annotation store, in the form projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/annotationStores/{annotation_store_id}). * The destination annotation store must be in the same project as the source data. De-identifying data across multiple projects is not supported. * The destination annotation store must exist when using DeidentifyDicomStore or DeidentifyFhirStore. DeidentifyDataset automatically creates the destination annotation store.
- store_quote bool
- If set to true, the sensitive texts are included in SensitiveTextAnnotation of Annotation.
- annotationStore StringName 
- The name of the annotation store, in the form projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/annotationStores/{annotation_store_id}). * The destination annotation store must be in the same project as the source data. De-identifying data across multiple projects is not supported. * The destination annotation store must exist when using DeidentifyDicomStore or DeidentifyFhirStore. DeidentifyDataset automatically creates the destination annotation store.
- storeQuote Boolean
- If set to true, the sensitive texts are included in SensitiveTextAnnotation of Annotation.
CharacterMaskConfigResponse   
- MaskingCharacter string
- Character to mask the sensitive values. If not supplied, defaults to "*".
- MaskingCharacter string
- Character to mask the sensitive values. If not supplied, defaults to "*".
- maskingCharacter String
- Character to mask the sensitive values. If not supplied, defaults to "*".
- maskingCharacter string
- Character to mask the sensitive values. If not supplied, defaults to "*".
- masking_character str
- Character to mask the sensitive values. If not supplied, defaults to "*".
- maskingCharacter String
- Character to mask the sensitive values. If not supplied, defaults to "*".
ConsentConfigResponse  
- AccessDetermination Pulumi.Log Config Google Native. Healthcare. V1Beta1. Inputs. Access Determination Log Config Response 
- Optional. Specifies how the server logs the consent-aware requests. If not specified, the AccessDeterminationLogConfig.LogLevel.MINIMUMoption is used.
- AccessEnforced bool
- Optional. If set to true, when accessing FHIR resources, the consent headers provided using SMART-on-FHIR will be verified against consents given by patients. See the ConsentEnforcementVersion for the supported consent headers.
- ConsentHeader Pulumi.Handling Google Native. Healthcare. V1Beta1. Inputs. Consent Header Handling Response 
- Optional. Different options to configure the behaviour of the server when handling the X-Consent-Scopeheader.
- EnforcedAdmin List<string>Consents 
- The versioned names of the enforced admin Consent resource(s), in the format projects/{project_id}/locations/{location}/datasets/{dataset_id}/fhirStores/{fhir_store_id}/fhir/Consent/{resource_id}/_history/{version_id}. For FHIR stores withdisable_resource_versioning=true, the format isprojects/{project_id}/locations/{location}/datasets/{dataset_id}/fhirStores/{fhir_store_id}/fhir/Consent/{resource_id}. This field can only be updated using ApplyAdminConsents.
- Version string
- Specifies which consent enforcement version is being used for this FHIR store. This field can only be set once by either CreateFhirStore or UpdateFhirStore. After that, you must call ApplyConsents to change the version.
- AccessDetermination AccessLog Config Determination Log Config Response 
- Optional. Specifies how the server logs the consent-aware requests. If not specified, the AccessDeterminationLogConfig.LogLevel.MINIMUMoption is used.
- AccessEnforced bool
- Optional. If set to true, when accessing FHIR resources, the consent headers provided using SMART-on-FHIR will be verified against consents given by patients. See the ConsentEnforcementVersion for the supported consent headers.
- ConsentHeader ConsentHandling Header Handling Response 
- Optional. Different options to configure the behaviour of the server when handling the X-Consent-Scopeheader.
- EnforcedAdmin []stringConsents 
- The versioned names of the enforced admin Consent resource(s), in the format projects/{project_id}/locations/{location}/datasets/{dataset_id}/fhirStores/{fhir_store_id}/fhir/Consent/{resource_id}/_history/{version_id}. For FHIR stores withdisable_resource_versioning=true, the format isprojects/{project_id}/locations/{location}/datasets/{dataset_id}/fhirStores/{fhir_store_id}/fhir/Consent/{resource_id}. This field can only be updated using ApplyAdminConsents.
- Version string
- Specifies which consent enforcement version is being used for this FHIR store. This field can only be set once by either CreateFhirStore or UpdateFhirStore. After that, you must call ApplyConsents to change the version.
- accessDetermination AccessLog Config Determination Log Config Response 
- Optional. Specifies how the server logs the consent-aware requests. If not specified, the AccessDeterminationLogConfig.LogLevel.MINIMUMoption is used.
- accessEnforced Boolean
- Optional. If set to true, when accessing FHIR resources, the consent headers provided using SMART-on-FHIR will be verified against consents given by patients. See the ConsentEnforcementVersion for the supported consent headers.
- consentHeader ConsentHandling Header Handling Response 
- Optional. Different options to configure the behaviour of the server when handling the X-Consent-Scopeheader.
- enforcedAdmin List<String>Consents 
- The versioned names of the enforced admin Consent resource(s), in the format projects/{project_id}/locations/{location}/datasets/{dataset_id}/fhirStores/{fhir_store_id}/fhir/Consent/{resource_id}/_history/{version_id}. For FHIR stores withdisable_resource_versioning=true, the format isprojects/{project_id}/locations/{location}/datasets/{dataset_id}/fhirStores/{fhir_store_id}/fhir/Consent/{resource_id}. This field can only be updated using ApplyAdminConsents.
- version String
- Specifies which consent enforcement version is being used for this FHIR store. This field can only be set once by either CreateFhirStore or UpdateFhirStore. After that, you must call ApplyConsents to change the version.
- accessDetermination AccessLog Config Determination Log Config Response 
- Optional. Specifies how the server logs the consent-aware requests. If not specified, the AccessDeterminationLogConfig.LogLevel.MINIMUMoption is used.
- accessEnforced boolean
- Optional. If set to true, when accessing FHIR resources, the consent headers provided using SMART-on-FHIR will be verified against consents given by patients. See the ConsentEnforcementVersion for the supported consent headers.
- consentHeader ConsentHandling Header Handling Response 
- Optional. Different options to configure the behaviour of the server when handling the X-Consent-Scopeheader.
- enforcedAdmin string[]Consents 
- The versioned names of the enforced admin Consent resource(s), in the format projects/{project_id}/locations/{location}/datasets/{dataset_id}/fhirStores/{fhir_store_id}/fhir/Consent/{resource_id}/_history/{version_id}. For FHIR stores withdisable_resource_versioning=true, the format isprojects/{project_id}/locations/{location}/datasets/{dataset_id}/fhirStores/{fhir_store_id}/fhir/Consent/{resource_id}. This field can only be updated using ApplyAdminConsents.
- version string
- Specifies which consent enforcement version is being used for this FHIR store. This field can only be set once by either CreateFhirStore or UpdateFhirStore. After that, you must call ApplyConsents to change the version.
- access_determination_ Accesslog_ config Determination Log Config Response 
- Optional. Specifies how the server logs the consent-aware requests. If not specified, the AccessDeterminationLogConfig.LogLevel.MINIMUMoption is used.
- access_enforced bool
- Optional. If set to true, when accessing FHIR resources, the consent headers provided using SMART-on-FHIR will be verified against consents given by patients. See the ConsentEnforcementVersion for the supported consent headers.
- consent_header_ Consenthandling Header Handling Response 
- Optional. Different options to configure the behaviour of the server when handling the X-Consent-Scopeheader.
- enforced_admin_ Sequence[str]consents 
- The versioned names of the enforced admin Consent resource(s), in the format projects/{project_id}/locations/{location}/datasets/{dataset_id}/fhirStores/{fhir_store_id}/fhir/Consent/{resource_id}/_history/{version_id}. For FHIR stores withdisable_resource_versioning=true, the format isprojects/{project_id}/locations/{location}/datasets/{dataset_id}/fhirStores/{fhir_store_id}/fhir/Consent/{resource_id}. This field can only be updated using ApplyAdminConsents.
- version str
- Specifies which consent enforcement version is being used for this FHIR store. This field can only be set once by either CreateFhirStore or UpdateFhirStore. After that, you must call ApplyConsents to change the version.
- accessDetermination Property MapLog Config 
- Optional. Specifies how the server logs the consent-aware requests. If not specified, the AccessDeterminationLogConfig.LogLevel.MINIMUMoption is used.
- accessEnforced Boolean
- Optional. If set to true, when accessing FHIR resources, the consent headers provided using SMART-on-FHIR will be verified against consents given by patients. See the ConsentEnforcementVersion for the supported consent headers.
- consentHeader Property MapHandling 
- Optional. Different options to configure the behaviour of the server when handling the X-Consent-Scopeheader.
- enforcedAdmin List<String>Consents 
- The versioned names of the enforced admin Consent resource(s), in the format projects/{project_id}/locations/{location}/datasets/{dataset_id}/fhirStores/{fhir_store_id}/fhir/Consent/{resource_id}/_history/{version_id}. For FHIR stores withdisable_resource_versioning=true, the format isprojects/{project_id}/locations/{location}/datasets/{dataset_id}/fhirStores/{fhir_store_id}/fhir/Consent/{resource_id}. This field can only be updated using ApplyAdminConsents.
- version String
- Specifies which consent enforcement version is being used for this FHIR store. This field can only be set once by either CreateFhirStore or UpdateFhirStore. After that, you must call ApplyConsents to change the version.
ConsentHeaderHandlingResponse   
- Profile string
- Optional. Specifies the default server behavior when the header is empty. If not specified, the ScopeProfile.PERMIT_EMPTY_SCOPEoption is used.
- Profile string
- Optional. Specifies the default server behavior when the header is empty. If not specified, the ScopeProfile.PERMIT_EMPTY_SCOPEoption is used.
- profile String
- Optional. Specifies the default server behavior when the header is empty. If not specified, the ScopeProfile.PERMIT_EMPTY_SCOPEoption is used.
- profile string
- Optional. Specifies the default server behavior when the header is empty. If not specified, the ScopeProfile.PERMIT_EMPTY_SCOPEoption is used.
- profile str
- Optional. Specifies the default server behavior when the header is empty. If not specified, the ScopeProfile.PERMIT_EMPTY_SCOPEoption is used.
- profile String
- Optional. Specifies the default server behavior when the header is empty. If not specified, the ScopeProfile.PERMIT_EMPTY_SCOPEoption is used.
CryptoHashConfigResponse   
- CryptoKey string
- An AES 128/192/256 bit key. Causes the hash to be computed based on this key. A default key is generated for each Deidentify operation and is used when neither crypto_key nor kms_wrapped is specified. Must not be set if kms_wrapped is set.
- KmsWrapped Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Kms Wrapped Crypto Key Response 
- KMS wrapped key. Must not be set if crypto_key is set.
- CryptoKey string
- An AES 128/192/256 bit key. Causes the hash to be computed based on this key. A default key is generated for each Deidentify operation and is used when neither crypto_key nor kms_wrapped is specified. Must not be set if kms_wrapped is set.
- KmsWrapped KmsWrapped Crypto Key Response 
- KMS wrapped key. Must not be set if crypto_key is set.
- cryptoKey String
- An AES 128/192/256 bit key. Causes the hash to be computed based on this key. A default key is generated for each Deidentify operation and is used when neither crypto_key nor kms_wrapped is specified. Must not be set if kms_wrapped is set.
- kmsWrapped KmsWrapped Crypto Key Response 
- KMS wrapped key. Must not be set if crypto_key is set.
- cryptoKey string
- An AES 128/192/256 bit key. Causes the hash to be computed based on this key. A default key is generated for each Deidentify operation and is used when neither crypto_key nor kms_wrapped is specified. Must not be set if kms_wrapped is set.
- kmsWrapped KmsWrapped Crypto Key Response 
- KMS wrapped key. Must not be set if crypto_key is set.
- crypto_key str
- An AES 128/192/256 bit key. Causes the hash to be computed based on this key. A default key is generated for each Deidentify operation and is used when neither crypto_key nor kms_wrapped is specified. Must not be set if kms_wrapped is set.
- kms_wrapped KmsWrapped Crypto Key Response 
- KMS wrapped key. Must not be set if crypto_key is set.
- cryptoKey String
- An AES 128/192/256 bit key. Causes the hash to be computed based on this key. A default key is generated for each Deidentify operation and is used when neither crypto_key nor kms_wrapped is specified. Must not be set if kms_wrapped is set.
- kmsWrapped Property Map
- KMS wrapped key. Must not be set if crypto_key is set.
DateShiftConfigResponse   
- CryptoKey string
- An AES 128/192/256 bit key. The date shift is computed based on this key and the patient ID. If the patient ID is empty for a DICOM resource, the date shift is computed based on this key and the study instance UID. If crypto_key is not set, then kms_wrapped is used to calculate the date shift. If neither is set, a default key is generated for each de-identify operation. Must not be set if kms_wrapped is set.
- KmsWrapped Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Kms Wrapped Crypto Key Response 
- KMS wrapped key. If kms_wrapped is not set, then crypto_key is used to calculate the date shift. If neither is set, a default key is generated for each de-identify operation. Must not be set if crypto_key is set.
- CryptoKey string
- An AES 128/192/256 bit key. The date shift is computed based on this key and the patient ID. If the patient ID is empty for a DICOM resource, the date shift is computed based on this key and the study instance UID. If crypto_key is not set, then kms_wrapped is used to calculate the date shift. If neither is set, a default key is generated for each de-identify operation. Must not be set if kms_wrapped is set.
- KmsWrapped KmsWrapped Crypto Key Response 
- KMS wrapped key. If kms_wrapped is not set, then crypto_key is used to calculate the date shift. If neither is set, a default key is generated for each de-identify operation. Must not be set if crypto_key is set.
- cryptoKey String
- An AES 128/192/256 bit key. The date shift is computed based on this key and the patient ID. If the patient ID is empty for a DICOM resource, the date shift is computed based on this key and the study instance UID. If crypto_key is not set, then kms_wrapped is used to calculate the date shift. If neither is set, a default key is generated for each de-identify operation. Must not be set if kms_wrapped is set.
- kmsWrapped KmsWrapped Crypto Key Response 
- KMS wrapped key. If kms_wrapped is not set, then crypto_key is used to calculate the date shift. If neither is set, a default key is generated for each de-identify operation. Must not be set if crypto_key is set.
- cryptoKey string
- An AES 128/192/256 bit key. The date shift is computed based on this key and the patient ID. If the patient ID is empty for a DICOM resource, the date shift is computed based on this key and the study instance UID. If crypto_key is not set, then kms_wrapped is used to calculate the date shift. If neither is set, a default key is generated for each de-identify operation. Must not be set if kms_wrapped is set.
- kmsWrapped KmsWrapped Crypto Key Response 
- KMS wrapped key. If kms_wrapped is not set, then crypto_key is used to calculate the date shift. If neither is set, a default key is generated for each de-identify operation. Must not be set if crypto_key is set.
- crypto_key str
- An AES 128/192/256 bit key. The date shift is computed based on this key and the patient ID. If the patient ID is empty for a DICOM resource, the date shift is computed based on this key and the study instance UID. If crypto_key is not set, then kms_wrapped is used to calculate the date shift. If neither is set, a default key is generated for each de-identify operation. Must not be set if kms_wrapped is set.
- kms_wrapped KmsWrapped Crypto Key Response 
- KMS wrapped key. If kms_wrapped is not set, then crypto_key is used to calculate the date shift. If neither is set, a default key is generated for each de-identify operation. Must not be set if crypto_key is set.
- cryptoKey String
- An AES 128/192/256 bit key. The date shift is computed based on this key and the patient ID. If the patient ID is empty for a DICOM resource, the date shift is computed based on this key and the study instance UID. If crypto_key is not set, then kms_wrapped is used to calculate the date shift. If neither is set, a default key is generated for each de-identify operation. Must not be set if kms_wrapped is set.
- kmsWrapped Property Map
- KMS wrapped key. If kms_wrapped is not set, then crypto_key is used to calculate the date shift. If neither is set, a default key is generated for each de-identify operation. Must not be set if crypto_key is set.
DeidentifiedStoreDestinationResponse   
- Config
Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Deidentify Config Response 
- The configuration to use when de-identifying resources that are added to this store.
- Store string
- The full resource name of a Cloud Healthcare FHIR store, for example, projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/fhirStores/{fhir_store_id}.
- Config
DeidentifyConfig Response 
- The configuration to use when de-identifying resources that are added to this store.
- Store string
- The full resource name of a Cloud Healthcare FHIR store, for example, projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/fhirStores/{fhir_store_id}.
- config
DeidentifyConfig Response 
- The configuration to use when de-identifying resources that are added to this store.
- store String
- The full resource name of a Cloud Healthcare FHIR store, for example, projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/fhirStores/{fhir_store_id}.
- config
DeidentifyConfig Response 
- The configuration to use when de-identifying resources that are added to this store.
- store string
- The full resource name of a Cloud Healthcare FHIR store, for example, projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/fhirStores/{fhir_store_id}.
- config
DeidentifyConfig Response 
- The configuration to use when de-identifying resources that are added to this store.
- store str
- The full resource name of a Cloud Healthcare FHIR store, for example, projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/fhirStores/{fhir_store_id}.
- config Property Map
- The configuration to use when de-identifying resources that are added to this store.
- store String
- The full resource name of a Cloud Healthcare FHIR store, for example, projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/fhirStores/{fhir_store_id}.
DeidentifyConfigResponse  
- Annotation
Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Annotation Config Response 
- Configures how annotations, meaning that the location and infoType of sensitive information findings, are created during de-identification. If unspecified, no annotations are created.
- Dicom
Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Dicom Config Response 
- Configures de-id of application/DICOM content. Deprecated. Use dicom_tag_configinstead.
- DicomTag Pulumi.Config Google Native. Healthcare. V1Beta1. Inputs. Dicom Tag Config Response 
- Configures de-id of application/DICOM content.
- Fhir
Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Fhir Config Response 
- Configures de-id of application/FHIR content. Deprecated. Use fhir_field_configinstead.
- FhirField Pulumi.Config Google Native. Healthcare. V1Beta1. Inputs. Fhir Field Config Response 
- Configures de-id of application/FHIR content.
- Image
Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Image Config Response 
- Configures the de-identification of image pixels in the source_dataset. Deprecated. Use dicom_tag_config.options.clean_imageinstead.
- OperationMetadata Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Deidentify Operation Metadata Response 
- Details about the work the de-identify operation performed.
- Text
Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Text Config Response 
- Configures de-identification of text wherever it is found in the source_dataset.
- UseRegional boolData Processing 
- Ensures in-flight data remains in the region of origin during de-identification. Using this option results in a significant reduction of throughput, and is not compatible with LOCATIONorORGANIZATION_NAMEinfoTypes. If the deprecated DicomConfig or FhirConfig are used, thenLOCATIONmust be excluded within TextConfig, and must also be excluded within ImageConfig if image redaction is required.
- Annotation
AnnotationConfig Response 
- Configures how annotations, meaning that the location and infoType of sensitive information findings, are created during de-identification. If unspecified, no annotations are created.
- Dicom
DicomConfig Response 
- Configures de-id of application/DICOM content. Deprecated. Use dicom_tag_configinstead.
- DicomTag DicomConfig Tag Config Response 
- Configures de-id of application/DICOM content.
- Fhir
FhirConfig Response 
- Configures de-id of application/FHIR content. Deprecated. Use fhir_field_configinstead.
- FhirField FhirConfig Field Config Response 
- Configures de-id of application/FHIR content.
- Image
ImageConfig Response 
- Configures the de-identification of image pixels in the source_dataset. Deprecated. Use dicom_tag_config.options.clean_imageinstead.
- OperationMetadata DeidentifyOperation Metadata Response 
- Details about the work the de-identify operation performed.
- Text
TextConfig Response 
- Configures de-identification of text wherever it is found in the source_dataset.
- UseRegional boolData Processing 
- Ensures in-flight data remains in the region of origin during de-identification. Using this option results in a significant reduction of throughput, and is not compatible with LOCATIONorORGANIZATION_NAMEinfoTypes. If the deprecated DicomConfig or FhirConfig are used, thenLOCATIONmust be excluded within TextConfig, and must also be excluded within ImageConfig if image redaction is required.
- annotation
AnnotationConfig Response 
- Configures how annotations, meaning that the location and infoType of sensitive information findings, are created during de-identification. If unspecified, no annotations are created.
- dicom
DicomConfig Response 
- Configures de-id of application/DICOM content. Deprecated. Use dicom_tag_configinstead.
- dicomTag DicomConfig Tag Config Response 
- Configures de-id of application/DICOM content.
- fhir
FhirConfig Response 
- Configures de-id of application/FHIR content. Deprecated. Use fhir_field_configinstead.
- fhirField FhirConfig Field Config Response 
- Configures de-id of application/FHIR content.
- image
ImageConfig Response 
- Configures the de-identification of image pixels in the source_dataset. Deprecated. Use dicom_tag_config.options.clean_imageinstead.
- operationMetadata DeidentifyOperation Metadata Response 
- Details about the work the de-identify operation performed.
- text
TextConfig Response 
- Configures de-identification of text wherever it is found in the source_dataset.
- useRegional BooleanData Processing 
- Ensures in-flight data remains in the region of origin during de-identification. Using this option results in a significant reduction of throughput, and is not compatible with LOCATIONorORGANIZATION_NAMEinfoTypes. If the deprecated DicomConfig or FhirConfig are used, thenLOCATIONmust be excluded within TextConfig, and must also be excluded within ImageConfig if image redaction is required.
- annotation
AnnotationConfig Response 
- Configures how annotations, meaning that the location and infoType of sensitive information findings, are created during de-identification. If unspecified, no annotations are created.
- dicom
DicomConfig Response 
- Configures de-id of application/DICOM content. Deprecated. Use dicom_tag_configinstead.
- dicomTag DicomConfig Tag Config Response 
- Configures de-id of application/DICOM content.
- fhir
FhirConfig Response 
- Configures de-id of application/FHIR content. Deprecated. Use fhir_field_configinstead.
- fhirField FhirConfig Field Config Response 
- Configures de-id of application/FHIR content.
- image
ImageConfig Response 
- Configures the de-identification of image pixels in the source_dataset. Deprecated. Use dicom_tag_config.options.clean_imageinstead.
- operationMetadata DeidentifyOperation Metadata Response 
- Details about the work the de-identify operation performed.
- text
TextConfig Response 
- Configures de-identification of text wherever it is found in the source_dataset.
- useRegional booleanData Processing 
- Ensures in-flight data remains in the region of origin during de-identification. Using this option results in a significant reduction of throughput, and is not compatible with LOCATIONorORGANIZATION_NAMEinfoTypes. If the deprecated DicomConfig or FhirConfig are used, thenLOCATIONmust be excluded within TextConfig, and must also be excluded within ImageConfig if image redaction is required.
- annotation
AnnotationConfig Response 
- Configures how annotations, meaning that the location and infoType of sensitive information findings, are created during de-identification. If unspecified, no annotations are created.
- dicom
DicomConfig Response 
- Configures de-id of application/DICOM content. Deprecated. Use dicom_tag_configinstead.
- dicom_tag_ Dicomconfig Tag Config Response 
- Configures de-id of application/DICOM content.
- fhir
FhirConfig Response 
- Configures de-id of application/FHIR content. Deprecated. Use fhir_field_configinstead.
- fhir_field_ Fhirconfig Field Config Response 
- Configures de-id of application/FHIR content.
- image
ImageConfig Response 
- Configures the de-identification of image pixels in the source_dataset. Deprecated. Use dicom_tag_config.options.clean_imageinstead.
- operation_metadata DeidentifyOperation Metadata Response 
- Details about the work the de-identify operation performed.
- text
TextConfig Response 
- Configures de-identification of text wherever it is found in the source_dataset.
- use_regional_ booldata_ processing 
- Ensures in-flight data remains in the region of origin during de-identification. Using this option results in a significant reduction of throughput, and is not compatible with LOCATIONorORGANIZATION_NAMEinfoTypes. If the deprecated DicomConfig or FhirConfig are used, thenLOCATIONmust be excluded within TextConfig, and must also be excluded within ImageConfig if image redaction is required.
- annotation Property Map
- Configures how annotations, meaning that the location and infoType of sensitive information findings, are created during de-identification. If unspecified, no annotations are created.
- dicom Property Map
- Configures de-id of application/DICOM content. Deprecated. Use dicom_tag_configinstead.
- dicomTag Property MapConfig 
- Configures de-id of application/DICOM content.
- fhir Property Map
- Configures de-id of application/FHIR content. Deprecated. Use fhir_field_configinstead.
- fhirField Property MapConfig 
- Configures de-id of application/FHIR content.
- image Property Map
- Configures the de-identification of image pixels in the source_dataset. Deprecated. Use dicom_tag_config.options.clean_imageinstead.
- operationMetadata Property Map
- Details about the work the de-identify operation performed.
- text Property Map
- Configures de-identification of text wherever it is found in the source_dataset.
- useRegional BooleanData Processing 
- Ensures in-flight data remains in the region of origin during de-identification. Using this option results in a significant reduction of throughput, and is not compatible with LOCATIONorORGANIZATION_NAMEinfoTypes. If the deprecated DicomConfig or FhirConfig are used, thenLOCATIONmust be excluded within TextConfig, and must also be excluded within ImageConfig if image redaction is required.
DeidentifyOperationMetadataResponse   
- FhirOutput Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Fhir Output Response 
- Details about the FHIR store to write the output to.
- FhirOutput FhirOutput Response 
- Details about the FHIR store to write the output to.
- fhirOutput FhirOutput Response 
- Details about the FHIR store to write the output to.
- fhirOutput FhirOutput Response 
- Details about the FHIR store to write the output to.
- fhir_output FhirOutput Response 
- Details about the FHIR store to write the output to.
- fhirOutput Property Map
- Details about the FHIR store to write the output to.
DicomConfigResponse  
- FilterProfile string
- Tag filtering profile that determines which tags to keep/remove.
- KeepList Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Tag Filter List Response 
- List of tags to keep. Remove all other tags.
- RemoveList Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Tag Filter List Response 
- List of tags to remove. Keep all other tags.
- SkipId boolRedaction 
- If true, skip replacing StudyInstanceUID, SeriesInstanceUID, SOPInstanceUID, and MediaStorageSOPInstanceUID and leave them untouched. The Cloud Healthcare API regenerates these UIDs by default based on the DICOM Standard's reasoning: "Whilst these UIDs cannot be mapped directly to an individual out of context, given access to the original images, or to a database of the original images containing the UIDs, it would be possible to recover the individual's identity." http://dicom.nema.org/medical/dicom/current/output/chtml/part15/sect_E.3.9.html
- FilterProfile string
- Tag filtering profile that determines which tags to keep/remove.
- KeepList TagFilter List Response 
- List of tags to keep. Remove all other tags.
- RemoveList TagFilter List Response 
- List of tags to remove. Keep all other tags.
- SkipId boolRedaction 
- If true, skip replacing StudyInstanceUID, SeriesInstanceUID, SOPInstanceUID, and MediaStorageSOPInstanceUID and leave them untouched. The Cloud Healthcare API regenerates these UIDs by default based on the DICOM Standard's reasoning: "Whilst these UIDs cannot be mapped directly to an individual out of context, given access to the original images, or to a database of the original images containing the UIDs, it would be possible to recover the individual's identity." http://dicom.nema.org/medical/dicom/current/output/chtml/part15/sect_E.3.9.html
- filterProfile String
- Tag filtering profile that determines which tags to keep/remove.
- keepList TagFilter List Response 
- List of tags to keep. Remove all other tags.
- removeList TagFilter List Response 
- List of tags to remove. Keep all other tags.
- skipId BooleanRedaction 
- If true, skip replacing StudyInstanceUID, SeriesInstanceUID, SOPInstanceUID, and MediaStorageSOPInstanceUID and leave them untouched. The Cloud Healthcare API regenerates these UIDs by default based on the DICOM Standard's reasoning: "Whilst these UIDs cannot be mapped directly to an individual out of context, given access to the original images, or to a database of the original images containing the UIDs, it would be possible to recover the individual's identity." http://dicom.nema.org/medical/dicom/current/output/chtml/part15/sect_E.3.9.html
- filterProfile string
- Tag filtering profile that determines which tags to keep/remove.
- keepList TagFilter List Response 
- List of tags to keep. Remove all other tags.
- removeList TagFilter List Response 
- List of tags to remove. Keep all other tags.
- skipId booleanRedaction 
- If true, skip replacing StudyInstanceUID, SeriesInstanceUID, SOPInstanceUID, and MediaStorageSOPInstanceUID and leave them untouched. The Cloud Healthcare API regenerates these UIDs by default based on the DICOM Standard's reasoning: "Whilst these UIDs cannot be mapped directly to an individual out of context, given access to the original images, or to a database of the original images containing the UIDs, it would be possible to recover the individual's identity." http://dicom.nema.org/medical/dicom/current/output/chtml/part15/sect_E.3.9.html
- filter_profile str
- Tag filtering profile that determines which tags to keep/remove.
- keep_list TagFilter List Response 
- List of tags to keep. Remove all other tags.
- remove_list TagFilter List Response 
- List of tags to remove. Keep all other tags.
- skip_id_ boolredaction 
- If true, skip replacing StudyInstanceUID, SeriesInstanceUID, SOPInstanceUID, and MediaStorageSOPInstanceUID and leave them untouched. The Cloud Healthcare API regenerates these UIDs by default based on the DICOM Standard's reasoning: "Whilst these UIDs cannot be mapped directly to an individual out of context, given access to the original images, or to a database of the original images containing the UIDs, it would be possible to recover the individual's identity." http://dicom.nema.org/medical/dicom/current/output/chtml/part15/sect_E.3.9.html
- filterProfile String
- Tag filtering profile that determines which tags to keep/remove.
- keepList Property Map
- List of tags to keep. Remove all other tags.
- removeList Property Map
- List of tags to remove. Keep all other tags.
- skipId BooleanRedaction 
- If true, skip replacing StudyInstanceUID, SeriesInstanceUID, SOPInstanceUID, and MediaStorageSOPInstanceUID and leave them untouched. The Cloud Healthcare API regenerates these UIDs by default based on the DICOM Standard's reasoning: "Whilst these UIDs cannot be mapped directly to an individual out of context, given access to the original images, or to a database of the original images containing the UIDs, it would be possible to recover the individual's identity." http://dicom.nema.org/medical/dicom/current/output/chtml/part15/sect_E.3.9.html
DicomTagConfigResponse   
- Actions
List<Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Action Response> 
- Specifies custom tag selections and Actionsto apply to them. Overridesoptionsandprofile. ConflictingActionsare applied in the order given.
- Options
Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Options Response 
- Specifies additional options to apply, overriding the base profile.
- ProfileType string
- Base profile type for handling DICOM tags.
- Actions
[]ActionResponse 
- Specifies custom tag selections and Actionsto apply to them. Overridesoptionsandprofile. ConflictingActionsare applied in the order given.
- Options
OptionsResponse 
- Specifies additional options to apply, overriding the base profile.
- ProfileType string
- Base profile type for handling DICOM tags.
- actions
List<ActionResponse> 
- Specifies custom tag selections and Actionsto apply to them. Overridesoptionsandprofile. ConflictingActionsare applied in the order given.
- options
OptionsResponse 
- Specifies additional options to apply, overriding the base profile.
- profileType String
- Base profile type for handling DICOM tags.
- actions
ActionResponse[] 
- Specifies custom tag selections and Actionsto apply to them. Overridesoptionsandprofile. ConflictingActionsare applied in the order given.
- options
OptionsResponse 
- Specifies additional options to apply, overriding the base profile.
- profileType string
- Base profile type for handling DICOM tags.
- actions
Sequence[ActionResponse] 
- Specifies custom tag selections and Actionsto apply to them. Overridesoptionsandprofile. ConflictingActionsare applied in the order given.
- options
OptionsResponse 
- Specifies additional options to apply, overriding the base profile.
- profile_type str
- Base profile type for handling DICOM tags.
- actions List<Property Map>
- Specifies custom tag selections and Actionsto apply to them. Overridesoptionsandprofile. ConflictingActionsare applied in the order given.
- options Property Map
- Specifies additional options to apply, overriding the base profile.
- profileType String
- Base profile type for handling DICOM tags.
FhirConfigResponse  
- DefaultKeep boolExtensions 
- The behaviour for handling FHIR extensions that aren't otherwise specified for de-identification. If true, all extensions are preserved during de-identification by default. If false or unspecified, all extensions are removed during de-identification by default.
- FieldMetadata List<Pulumi.List Google Native. Healthcare. V1Beta1. Inputs. Field Metadata Response> 
- Specifies FHIR paths to match and how to transform them. Any field that is not matched by a FieldMetadata is passed through to the output dataset unmodified. All extensions will be processed according to default_keep_extensions. If a field can be matched by more than one FieldMetadata, the first FieldMetadata.Action is applied.
- DefaultKeep boolExtensions 
- The behaviour for handling FHIR extensions that aren't otherwise specified for de-identification. If true, all extensions are preserved during de-identification by default. If false or unspecified, all extensions are removed during de-identification by default.
- FieldMetadata []FieldList Metadata Response 
- Specifies FHIR paths to match and how to transform them. Any field that is not matched by a FieldMetadata is passed through to the output dataset unmodified. All extensions will be processed according to default_keep_extensions. If a field can be matched by more than one FieldMetadata, the first FieldMetadata.Action is applied.
- defaultKeep BooleanExtensions 
- The behaviour for handling FHIR extensions that aren't otherwise specified for de-identification. If true, all extensions are preserved during de-identification by default. If false or unspecified, all extensions are removed during de-identification by default.
- fieldMetadata List<FieldList Metadata Response> 
- Specifies FHIR paths to match and how to transform them. Any field that is not matched by a FieldMetadata is passed through to the output dataset unmodified. All extensions will be processed according to default_keep_extensions. If a field can be matched by more than one FieldMetadata, the first FieldMetadata.Action is applied.
- defaultKeep booleanExtensions 
- The behaviour for handling FHIR extensions that aren't otherwise specified for de-identification. If true, all extensions are preserved during de-identification by default. If false or unspecified, all extensions are removed during de-identification by default.
- fieldMetadata FieldList Metadata Response[] 
- Specifies FHIR paths to match and how to transform them. Any field that is not matched by a FieldMetadata is passed through to the output dataset unmodified. All extensions will be processed according to default_keep_extensions. If a field can be matched by more than one FieldMetadata, the first FieldMetadata.Action is applied.
- default_keep_ boolextensions 
- The behaviour for handling FHIR extensions that aren't otherwise specified for de-identification. If true, all extensions are preserved during de-identification by default. If false or unspecified, all extensions are removed during de-identification by default.
- field_metadata_ Sequence[Fieldlist Metadata Response] 
- Specifies FHIR paths to match and how to transform them. Any field that is not matched by a FieldMetadata is passed through to the output dataset unmodified. All extensions will be processed according to default_keep_extensions. If a field can be matched by more than one FieldMetadata, the first FieldMetadata.Action is applied.
- defaultKeep BooleanExtensions 
- The behaviour for handling FHIR extensions that aren't otherwise specified for de-identification. If true, all extensions are preserved during de-identification by default. If false or unspecified, all extensions are removed during de-identification by default.
- fieldMetadata List<Property Map>List 
- Specifies FHIR paths to match and how to transform them. Any field that is not matched by a FieldMetadata is passed through to the output dataset unmodified. All extensions will be processed according to default_keep_extensions. If a field can be matched by more than one FieldMetadata, the first FieldMetadata.Action is applied.
FhirFieldConfigResponse   
- FieldMetadata List<Pulumi.List Google Native. Healthcare. V1Beta1. Inputs. Google Cloud Healthcare V1beta1Deidentify Field Metadata Response> 
- Specifies FHIR paths to match and how to transform them. Any field that is not matched by a FieldMetadata actionis passed through to the output dataset unmodified. All extensions will be processed according to keep_extensions. If a field can be matched by more than one FieldMetadataaction, the firstactionoption is applied. Overrides options and the union fieldprofilein FhirFieldConfig.
- Options
Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Google Cloud Healthcare V1beta1Deidentify Options Response 
- Specifies additional options, overriding the base ProfileType.
- ProfileType string
- Base profile type for handling FHIR fields.
- FieldMetadata []GoogleList Cloud Healthcare V1beta1Deidentify Field Metadata Response 
- Specifies FHIR paths to match and how to transform them. Any field that is not matched by a FieldMetadata actionis passed through to the output dataset unmodified. All extensions will be processed according to keep_extensions. If a field can be matched by more than one FieldMetadataaction, the firstactionoption is applied. Overrides options and the union fieldprofilein FhirFieldConfig.
- Options
GoogleCloud Healthcare V1beta1Deidentify Options Response 
- Specifies additional options, overriding the base ProfileType.
- ProfileType string
- Base profile type for handling FHIR fields.
- fieldMetadata List<GoogleList Cloud Healthcare V1beta1Deidentify Field Metadata Response> 
- Specifies FHIR paths to match and how to transform them. Any field that is not matched by a FieldMetadata actionis passed through to the output dataset unmodified. All extensions will be processed according to keep_extensions. If a field can be matched by more than one FieldMetadataaction, the firstactionoption is applied. Overrides options and the union fieldprofilein FhirFieldConfig.
- options
GoogleCloud Healthcare V1beta1Deidentify Options Response 
- Specifies additional options, overriding the base ProfileType.
- profileType String
- Base profile type for handling FHIR fields.
- fieldMetadata GoogleList Cloud Healthcare V1beta1Deidentify Field Metadata Response[] 
- Specifies FHIR paths to match and how to transform them. Any field that is not matched by a FieldMetadata actionis passed through to the output dataset unmodified. All extensions will be processed according to keep_extensions. If a field can be matched by more than one FieldMetadataaction, the firstactionoption is applied. Overrides options and the union fieldprofilein FhirFieldConfig.
- options
GoogleCloud Healthcare V1beta1Deidentify Options Response 
- Specifies additional options, overriding the base ProfileType.
- profileType string
- Base profile type for handling FHIR fields.
- field_metadata_ Sequence[Googlelist Cloud Healthcare V1beta1Deidentify Field Metadata Response] 
- Specifies FHIR paths to match and how to transform them. Any field that is not matched by a FieldMetadata actionis passed through to the output dataset unmodified. All extensions will be processed according to keep_extensions. If a field can be matched by more than one FieldMetadataaction, the firstactionoption is applied. Overrides options and the union fieldprofilein FhirFieldConfig.
- options
GoogleCloud Healthcare V1beta1Deidentify Options Response 
- Specifies additional options, overriding the base ProfileType.
- profile_type str
- Base profile type for handling FHIR fields.
- fieldMetadata List<Property Map>List 
- Specifies FHIR paths to match and how to transform them. Any field that is not matched by a FieldMetadata actionis passed through to the output dataset unmodified. All extensions will be processed according to keep_extensions. If a field can be matched by more than one FieldMetadataaction, the firstactionoption is applied. Overrides options and the union fieldprofilein FhirFieldConfig.
- options Property Map
- Specifies additional options, overriding the base ProfileType.
- profileType String
- Base profile type for handling FHIR fields.
FhirNotificationConfigResponse   
- PubsubTopic string
- The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a PubsubMessagewith the following fields: *PubsubMessage.Datacontains the resource name. *PubsubMessage.MessageIdis the ID of this notification. It is guaranteed to be unique within the topic. *PubsubMessage.PublishTimeis the time when the message was published. Note that notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. The Cloud Healthcare API service account, service-@gcp-sa-healthcare.iam.gserviceaccount.com, must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail (https://cloud.google.com/healthcare-api/docs/permissions-healthcare-api-gcp-products#dicom_fhir_and_hl7v2_store_cloud_pubsub_permissions). If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging.
- SendFull boolResource 
- Whether to send full FHIR resource to this Pub/Sub topic for Create and Update operation. Note that setting this to true does not guarantee that all resources will be sent in the format of full FHIR resource. When a resource change is too large or during heavy traffic, only the resource name will be sent. Clients should always check the "payloadType" label from a Pub/Sub message to determine whether it needs to fetch the full resource as a separate operation.
- SendPrevious boolResource On Delete 
- Whether to send full FHIR resource to this Pub/Sub topic for deleting FHIR resource. Note that setting this to true does not guarantee that all previous resources will be sent in the format of full FHIR resource. When a resource change is too large or during heavy traffic, only the resource name will be sent. Clients should always check the "payloadType" label from a Pub/Sub message to determine whether it needs to fetch the full previous resource as a separate operation.
- PubsubTopic string
- The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a PubsubMessagewith the following fields: *PubsubMessage.Datacontains the resource name. *PubsubMessage.MessageIdis the ID of this notification. It is guaranteed to be unique within the topic. *PubsubMessage.PublishTimeis the time when the message was published. Note that notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. The Cloud Healthcare API service account, service-@gcp-sa-healthcare.iam.gserviceaccount.com, must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail (https://cloud.google.com/healthcare-api/docs/permissions-healthcare-api-gcp-products#dicom_fhir_and_hl7v2_store_cloud_pubsub_permissions). If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging.
- SendFull boolResource 
- Whether to send full FHIR resource to this Pub/Sub topic for Create and Update operation. Note that setting this to true does not guarantee that all resources will be sent in the format of full FHIR resource. When a resource change is too large or during heavy traffic, only the resource name will be sent. Clients should always check the "payloadType" label from a Pub/Sub message to determine whether it needs to fetch the full resource as a separate operation.
- SendPrevious boolResource On Delete 
- Whether to send full FHIR resource to this Pub/Sub topic for deleting FHIR resource. Note that setting this to true does not guarantee that all previous resources will be sent in the format of full FHIR resource. When a resource change is too large or during heavy traffic, only the resource name will be sent. Clients should always check the "payloadType" label from a Pub/Sub message to determine whether it needs to fetch the full previous resource as a separate operation.
- pubsubTopic String
- The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a PubsubMessagewith the following fields: *PubsubMessage.Datacontains the resource name. *PubsubMessage.MessageIdis the ID of this notification. It is guaranteed to be unique within the topic. *PubsubMessage.PublishTimeis the time when the message was published. Note that notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. The Cloud Healthcare API service account, service-@gcp-sa-healthcare.iam.gserviceaccount.com, must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail (https://cloud.google.com/healthcare-api/docs/permissions-healthcare-api-gcp-products#dicom_fhir_and_hl7v2_store_cloud_pubsub_permissions). If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging.
- sendFull BooleanResource 
- Whether to send full FHIR resource to this Pub/Sub topic for Create and Update operation. Note that setting this to true does not guarantee that all resources will be sent in the format of full FHIR resource. When a resource change is too large or during heavy traffic, only the resource name will be sent. Clients should always check the "payloadType" label from a Pub/Sub message to determine whether it needs to fetch the full resource as a separate operation.
- sendPrevious BooleanResource On Delete 
- Whether to send full FHIR resource to this Pub/Sub topic for deleting FHIR resource. Note that setting this to true does not guarantee that all previous resources will be sent in the format of full FHIR resource. When a resource change is too large or during heavy traffic, only the resource name will be sent. Clients should always check the "payloadType" label from a Pub/Sub message to determine whether it needs to fetch the full previous resource as a separate operation.
- pubsubTopic string
- The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a PubsubMessagewith the following fields: *PubsubMessage.Datacontains the resource name. *PubsubMessage.MessageIdis the ID of this notification. It is guaranteed to be unique within the topic. *PubsubMessage.PublishTimeis the time when the message was published. Note that notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. The Cloud Healthcare API service account, service-@gcp-sa-healthcare.iam.gserviceaccount.com, must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail (https://cloud.google.com/healthcare-api/docs/permissions-healthcare-api-gcp-products#dicom_fhir_and_hl7v2_store_cloud_pubsub_permissions). If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging.
- sendFull booleanResource 
- Whether to send full FHIR resource to this Pub/Sub topic for Create and Update operation. Note that setting this to true does not guarantee that all resources will be sent in the format of full FHIR resource. When a resource change is too large or during heavy traffic, only the resource name will be sent. Clients should always check the "payloadType" label from a Pub/Sub message to determine whether it needs to fetch the full resource as a separate operation.
- sendPrevious booleanResource On Delete 
- Whether to send full FHIR resource to this Pub/Sub topic for deleting FHIR resource. Note that setting this to true does not guarantee that all previous resources will be sent in the format of full FHIR resource. When a resource change is too large or during heavy traffic, only the resource name will be sent. Clients should always check the "payloadType" label from a Pub/Sub message to determine whether it needs to fetch the full previous resource as a separate operation.
- pubsub_topic str
- The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a PubsubMessagewith the following fields: *PubsubMessage.Datacontains the resource name. *PubsubMessage.MessageIdis the ID of this notification. It is guaranteed to be unique within the topic. *PubsubMessage.PublishTimeis the time when the message was published. Note that notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. The Cloud Healthcare API service account, service-@gcp-sa-healthcare.iam.gserviceaccount.com, must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail (https://cloud.google.com/healthcare-api/docs/permissions-healthcare-api-gcp-products#dicom_fhir_and_hl7v2_store_cloud_pubsub_permissions). If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging.
- send_full_ boolresource 
- Whether to send full FHIR resource to this Pub/Sub topic for Create and Update operation. Note that setting this to true does not guarantee that all resources will be sent in the format of full FHIR resource. When a resource change is too large or during heavy traffic, only the resource name will be sent. Clients should always check the "payloadType" label from a Pub/Sub message to determine whether it needs to fetch the full resource as a separate operation.
- send_previous_ boolresource_ on_ delete 
- Whether to send full FHIR resource to this Pub/Sub topic for deleting FHIR resource. Note that setting this to true does not guarantee that all previous resources will be sent in the format of full FHIR resource. When a resource change is too large or during heavy traffic, only the resource name will be sent. Clients should always check the "payloadType" label from a Pub/Sub message to determine whether it needs to fetch the full previous resource as a separate operation.
- pubsubTopic String
- The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a PubsubMessagewith the following fields: *PubsubMessage.Datacontains the resource name. *PubsubMessage.MessageIdis the ID of this notification. It is guaranteed to be unique within the topic. *PubsubMessage.PublishTimeis the time when the message was published. Note that notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. The Cloud Healthcare API service account, service-@gcp-sa-healthcare.iam.gserviceaccount.com, must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail (https://cloud.google.com/healthcare-api/docs/permissions-healthcare-api-gcp-products#dicom_fhir_and_hl7v2_store_cloud_pubsub_permissions). If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging.
- sendFull BooleanResource 
- Whether to send full FHIR resource to this Pub/Sub topic for Create and Update operation. Note that setting this to true does not guarantee that all resources will be sent in the format of full FHIR resource. When a resource change is too large or during heavy traffic, only the resource name will be sent. Clients should always check the "payloadType" label from a Pub/Sub message to determine whether it needs to fetch the full resource as a separate operation.
- sendPrevious BooleanResource On Delete 
- Whether to send full FHIR resource to this Pub/Sub topic for deleting FHIR resource. Note that setting this to true does not guarantee that all previous resources will be sent in the format of full FHIR resource. When a resource change is too large or during heavy traffic, only the resource name will be sent. Clients should always check the "payloadType" label from a Pub/Sub message to determine whether it needs to fetch the full previous resource as a separate operation.
FhirOutputResponse  
- FhirStore string
- Name of the output FHIR store, which must already exist. You must grant the healthcare.fhirResources.update permission on the destination store to your project's Cloud Healthcare Service Agent service account. The destination store must set enableUpdateCreate to true. The destination store must use FHIR version R4. Writing these resources will consume FHIR operations quota from the project containing the source data. De-identify operation metadata is only generated for DICOM de-identification operations.
- FhirStore string
- Name of the output FHIR store, which must already exist. You must grant the healthcare.fhirResources.update permission on the destination store to your project's Cloud Healthcare Service Agent service account. The destination store must set enableUpdateCreate to true. The destination store must use FHIR version R4. Writing these resources will consume FHIR operations quota from the project containing the source data. De-identify operation metadata is only generated for DICOM de-identification operations.
- fhirStore String
- Name of the output FHIR store, which must already exist. You must grant the healthcare.fhirResources.update permission on the destination store to your project's Cloud Healthcare Service Agent service account. The destination store must set enableUpdateCreate to true. The destination store must use FHIR version R4. Writing these resources will consume FHIR operations quota from the project containing the source data. De-identify operation metadata is only generated for DICOM de-identification operations.
- fhirStore string
- Name of the output FHIR store, which must already exist. You must grant the healthcare.fhirResources.update permission on the destination store to your project's Cloud Healthcare Service Agent service account. The destination store must set enableUpdateCreate to true. The destination store must use FHIR version R4. Writing these resources will consume FHIR operations quota from the project containing the source data. De-identify operation metadata is only generated for DICOM de-identification operations.
- fhir_store str
- Name of the output FHIR store, which must already exist. You must grant the healthcare.fhirResources.update permission on the destination store to your project's Cloud Healthcare Service Agent service account. The destination store must set enableUpdateCreate to true. The destination store must use FHIR version R4. Writing these resources will consume FHIR operations quota from the project containing the source data. De-identify operation metadata is only generated for DICOM de-identification operations.
- fhirStore String
- Name of the output FHIR store, which must already exist. You must grant the healthcare.fhirResources.update permission on the destination store to your project's Cloud Healthcare Service Agent service account. The destination store must set enableUpdateCreate to true. The destination store must use FHIR version R4. Writing these resources will consume FHIR operations quota from the project containing the source data. De-identify operation metadata is only generated for DICOM de-identification operations.
FieldMetadataResponse  
- Action string
- Deidentify action for one field.
- Paths List<string>
- List of paths to FHIR fields to redact. Each path is a period-separated list where each component is either a field name or FHIR type name. All types begin with an upper case letter. For example, the resource field "Patient.Address.city", which uses a string type, can be matched by "Patient.Address.String". Path also supports partial matching. For example, "Patient.Address.city" can be matched by "Address.city" (Patient omitted). Partial matching and type matching can be combined. For example, "Patient.Address.city" can be matched by "Address.String". For "choice" types (those defined in the FHIR spec with the form: field[x]), use two separate components. For example, "deceasedAge.unit" is matched by "Deceased.Age.unit". Supported types are: AdministrativeGenderCode, Base64Binary, Boolean, Code, Date, DateTime, Decimal, HumanName, Id, Instant, Integer, LanguageCode, Markdown, Oid, PositiveInt, String, UnsignedInt, Uri, Uuid, Xhtml. The sub-type for HumanName(for example HumanName.given, HumanName.family) can be omitted.
- Action string
- Deidentify action for one field.
- Paths []string
- List of paths to FHIR fields to redact. Each path is a period-separated list where each component is either a field name or FHIR type name. All types begin with an upper case letter. For example, the resource field "Patient.Address.city", which uses a string type, can be matched by "Patient.Address.String". Path also supports partial matching. For example, "Patient.Address.city" can be matched by "Address.city" (Patient omitted). Partial matching and type matching can be combined. For example, "Patient.Address.city" can be matched by "Address.String". For "choice" types (those defined in the FHIR spec with the form: field[x]), use two separate components. For example, "deceasedAge.unit" is matched by "Deceased.Age.unit". Supported types are: AdministrativeGenderCode, Base64Binary, Boolean, Code, Date, DateTime, Decimal, HumanName, Id, Instant, Integer, LanguageCode, Markdown, Oid, PositiveInt, String, UnsignedInt, Uri, Uuid, Xhtml. The sub-type for HumanName(for example HumanName.given, HumanName.family) can be omitted.
- action String
- Deidentify action for one field.
- paths List<String>
- List of paths to FHIR fields to redact. Each path is a period-separated list where each component is either a field name or FHIR type name. All types begin with an upper case letter. For example, the resource field "Patient.Address.city", which uses a string type, can be matched by "Patient.Address.String". Path also supports partial matching. For example, "Patient.Address.city" can be matched by "Address.city" (Patient omitted). Partial matching and type matching can be combined. For example, "Patient.Address.city" can be matched by "Address.String". For "choice" types (those defined in the FHIR spec with the form: field[x]), use two separate components. For example, "deceasedAge.unit" is matched by "Deceased.Age.unit". Supported types are: AdministrativeGenderCode, Base64Binary, Boolean, Code, Date, DateTime, Decimal, HumanName, Id, Instant, Integer, LanguageCode, Markdown, Oid, PositiveInt, String, UnsignedInt, Uri, Uuid, Xhtml. The sub-type for HumanName(for example HumanName.given, HumanName.family) can be omitted.
- action string
- Deidentify action for one field.
- paths string[]
- List of paths to FHIR fields to redact. Each path is a period-separated list where each component is either a field name or FHIR type name. All types begin with an upper case letter. For example, the resource field "Patient.Address.city", which uses a string type, can be matched by "Patient.Address.String". Path also supports partial matching. For example, "Patient.Address.city" can be matched by "Address.city" (Patient omitted). Partial matching and type matching can be combined. For example, "Patient.Address.city" can be matched by "Address.String". For "choice" types (those defined in the FHIR spec with the form: field[x]), use two separate components. For example, "deceasedAge.unit" is matched by "Deceased.Age.unit". Supported types are: AdministrativeGenderCode, Base64Binary, Boolean, Code, Date, DateTime, Decimal, HumanName, Id, Instant, Integer, LanguageCode, Markdown, Oid, PositiveInt, String, UnsignedInt, Uri, Uuid, Xhtml. The sub-type for HumanName(for example HumanName.given, HumanName.family) can be omitted.
- action str
- Deidentify action for one field.
- paths Sequence[str]
- List of paths to FHIR fields to redact. Each path is a period-separated list where each component is either a field name or FHIR type name. All types begin with an upper case letter. For example, the resource field "Patient.Address.city", which uses a string type, can be matched by "Patient.Address.String". Path also supports partial matching. For example, "Patient.Address.city" can be matched by "Address.city" (Patient omitted). Partial matching and type matching can be combined. For example, "Patient.Address.city" can be matched by "Address.String". For "choice" types (those defined in the FHIR spec with the form: field[x]), use two separate components. For example, "deceasedAge.unit" is matched by "Deceased.Age.unit". Supported types are: AdministrativeGenderCode, Base64Binary, Boolean, Code, Date, DateTime, Decimal, HumanName, Id, Instant, Integer, LanguageCode, Markdown, Oid, PositiveInt, String, UnsignedInt, Uri, Uuid, Xhtml. The sub-type for HumanName(for example HumanName.given, HumanName.family) can be omitted.
- action String
- Deidentify action for one field.
- paths List<String>
- List of paths to FHIR fields to redact. Each path is a period-separated list where each component is either a field name or FHIR type name. All types begin with an upper case letter. For example, the resource field "Patient.Address.city", which uses a string type, can be matched by "Patient.Address.String". Path also supports partial matching. For example, "Patient.Address.city" can be matched by "Address.city" (Patient omitted). Partial matching and type matching can be combined. For example, "Patient.Address.city" can be matched by "Address.String". For "choice" types (those defined in the FHIR spec with the form: field[x]), use two separate components. For example, "deceasedAge.unit" is matched by "Deceased.Age.unit". Supported types are: AdministrativeGenderCode, Base64Binary, Boolean, Code, Date, DateTime, Decimal, HumanName, Id, Instant, Integer, LanguageCode, Markdown, Oid, PositiveInt, String, UnsignedInt, Uri, Uuid, Xhtml. The sub-type for HumanName(for example HumanName.given, HumanName.family) can be omitted.
GoogleCloudHealthcareV1beta1DeidentifyFieldMetadataResponse      
- CharacterMask Pulumi.Field Google Native. Healthcare. V1Beta1. Inputs. Character Mask Field Response 
- Replace the field's value with a masking character. Supported types: Code, Decimal, HumanName, Id, LanguageCode, Markdown, Oid, String, Uri, Uuid, Xhtml.
- CleanText Pulumi.Field Google Native. Healthcare. V1Beta1. Inputs. Clean Text Field Response 
- Inspect the field's text and transform sensitive text. Configure using TextConfig. Supported types: Code, Date, DateTime, Decimal, HumanName, Id, LanguageCode, Markdown, Oid, String, Uri, Uuid, Xhtml.
- CryptoHash Pulumi.Field Google Native. Healthcare. V1Beta1. Inputs. Crypto Hash Field Response 
- Replace field value with a hash of that value. Supported types: Code, Decimal, HumanName, Id, LanguageCode, Markdown, Oid, String, Uri, Uuid, Xhtml.
- DateShift Pulumi.Field Google Native. Healthcare. V1Beta1. Inputs. Date Shift Field Response 
- Shift the date by a randomized number of days. See date shifting for more information. Supported types: Date, DateTime.
- KeepField Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Keep Field Response 
- Keep the field unchanged.
- Paths List<string>
- List of paths to FHIR fields to redact. Each path is a period-separated list where each component is either a field name or FHIR type name. All types begin with an upper case letter. For example, the resource field Patient.Address.city, which uses a string type, can be matched byPatient.Address.String. Partial matching is supported. For example,Patient.Address.citycan be matched byAddress.city(withPatientomitted). Partial matching and type matching can be combined, for examplePatient.Address.citycan be matched byAddress.String. For "choice" types (those defined in the FHIR spec with the formatfield[x]), use two separate components. For example,deceasedAge.unitis matched byDeceased.Age.unit. The following types are supported: AdministrativeGenderCode, Base64Binary, Boolean, Code, Date, DateTime, Decimal, HumanName, Id, Instant, Integer, LanguageCode, Markdown, Oid, PositiveInt, String, UnsignedInt, Uri, Uuid, Xhtml. The sub-type for HumanName (for exampleHumanName.given,HumanName.family) can be omitted.
- RemoveField Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Remove Field Response 
- Remove the field.
- CharacterMask CharacterField Mask Field Response 
- Replace the field's value with a masking character. Supported types: Code, Decimal, HumanName, Id, LanguageCode, Markdown, Oid, String, Uri, Uuid, Xhtml.
- CleanText CleanField Text Field Response 
- Inspect the field's text and transform sensitive text. Configure using TextConfig. Supported types: Code, Date, DateTime, Decimal, HumanName, Id, LanguageCode, Markdown, Oid, String, Uri, Uuid, Xhtml.
- CryptoHash CryptoField Hash Field Response 
- Replace field value with a hash of that value. Supported types: Code, Decimal, HumanName, Id, LanguageCode, Markdown, Oid, String, Uri, Uuid, Xhtml.
- DateShift DateField Shift Field Response 
- Shift the date by a randomized number of days. See date shifting for more information. Supported types: Date, DateTime.
- KeepField KeepField Response 
- Keep the field unchanged.
- Paths []string
- List of paths to FHIR fields to redact. Each path is a period-separated list where each component is either a field name or FHIR type name. All types begin with an upper case letter. For example, the resource field Patient.Address.city, which uses a string type, can be matched byPatient.Address.String. Partial matching is supported. For example,Patient.Address.citycan be matched byAddress.city(withPatientomitted). Partial matching and type matching can be combined, for examplePatient.Address.citycan be matched byAddress.String. For "choice" types (those defined in the FHIR spec with the formatfield[x]), use two separate components. For example,deceasedAge.unitis matched byDeceased.Age.unit. The following types are supported: AdministrativeGenderCode, Base64Binary, Boolean, Code, Date, DateTime, Decimal, HumanName, Id, Instant, Integer, LanguageCode, Markdown, Oid, PositiveInt, String, UnsignedInt, Uri, Uuid, Xhtml. The sub-type for HumanName (for exampleHumanName.given,HumanName.family) can be omitted.
- RemoveField RemoveField Response 
- Remove the field.
- characterMask CharacterField Mask Field Response 
- Replace the field's value with a masking character. Supported types: Code, Decimal, HumanName, Id, LanguageCode, Markdown, Oid, String, Uri, Uuid, Xhtml.
- cleanText CleanField Text Field Response 
- Inspect the field's text and transform sensitive text. Configure using TextConfig. Supported types: Code, Date, DateTime, Decimal, HumanName, Id, LanguageCode, Markdown, Oid, String, Uri, Uuid, Xhtml.
- cryptoHash CryptoField Hash Field Response 
- Replace field value with a hash of that value. Supported types: Code, Decimal, HumanName, Id, LanguageCode, Markdown, Oid, String, Uri, Uuid, Xhtml.
- dateShift DateField Shift Field Response 
- Shift the date by a randomized number of days. See date shifting for more information. Supported types: Date, DateTime.
- keepField KeepField Response 
- Keep the field unchanged.
- paths List<String>
- List of paths to FHIR fields to redact. Each path is a period-separated list where each component is either a field name or FHIR type name. All types begin with an upper case letter. For example, the resource field Patient.Address.city, which uses a string type, can be matched byPatient.Address.String. Partial matching is supported. For example,Patient.Address.citycan be matched byAddress.city(withPatientomitted). Partial matching and type matching can be combined, for examplePatient.Address.citycan be matched byAddress.String. For "choice" types (those defined in the FHIR spec with the formatfield[x]), use two separate components. For example,deceasedAge.unitis matched byDeceased.Age.unit. The following types are supported: AdministrativeGenderCode, Base64Binary, Boolean, Code, Date, DateTime, Decimal, HumanName, Id, Instant, Integer, LanguageCode, Markdown, Oid, PositiveInt, String, UnsignedInt, Uri, Uuid, Xhtml. The sub-type for HumanName (for exampleHumanName.given,HumanName.family) can be omitted.
- removeField RemoveField Response 
- Remove the field.
- characterMask CharacterField Mask Field Response 
- Replace the field's value with a masking character. Supported types: Code, Decimal, HumanName, Id, LanguageCode, Markdown, Oid, String, Uri, Uuid, Xhtml.
- cleanText CleanField Text Field Response 
- Inspect the field's text and transform sensitive text. Configure using TextConfig. Supported types: Code, Date, DateTime, Decimal, HumanName, Id, LanguageCode, Markdown, Oid, String, Uri, Uuid, Xhtml.
- cryptoHash CryptoField Hash Field Response 
- Replace field value with a hash of that value. Supported types: Code, Decimal, HumanName, Id, LanguageCode, Markdown, Oid, String, Uri, Uuid, Xhtml.
- dateShift DateField Shift Field Response 
- Shift the date by a randomized number of days. See date shifting for more information. Supported types: Date, DateTime.
- keepField KeepField Response 
- Keep the field unchanged.
- paths string[]
- List of paths to FHIR fields to redact. Each path is a period-separated list where each component is either a field name or FHIR type name. All types begin with an upper case letter. For example, the resource field Patient.Address.city, which uses a string type, can be matched byPatient.Address.String. Partial matching is supported. For example,Patient.Address.citycan be matched byAddress.city(withPatientomitted). Partial matching and type matching can be combined, for examplePatient.Address.citycan be matched byAddress.String. For "choice" types (those defined in the FHIR spec with the formatfield[x]), use two separate components. For example,deceasedAge.unitis matched byDeceased.Age.unit. The following types are supported: AdministrativeGenderCode, Base64Binary, Boolean, Code, Date, DateTime, Decimal, HumanName, Id, Instant, Integer, LanguageCode, Markdown, Oid, PositiveInt, String, UnsignedInt, Uri, Uuid, Xhtml. The sub-type for HumanName (for exampleHumanName.given,HumanName.family) can be omitted.
- removeField RemoveField Response 
- Remove the field.
- character_mask_ Characterfield Mask Field Response 
- Replace the field's value with a masking character. Supported types: Code, Decimal, HumanName, Id, LanguageCode, Markdown, Oid, String, Uri, Uuid, Xhtml.
- clean_text_ Cleanfield Text Field Response 
- Inspect the field's text and transform sensitive text. Configure using TextConfig. Supported types: Code, Date, DateTime, Decimal, HumanName, Id, LanguageCode, Markdown, Oid, String, Uri, Uuid, Xhtml.
- crypto_hash_ Cryptofield Hash Field Response 
- Replace field value with a hash of that value. Supported types: Code, Decimal, HumanName, Id, LanguageCode, Markdown, Oid, String, Uri, Uuid, Xhtml.
- date_shift_ Datefield Shift Field Response 
- Shift the date by a randomized number of days. See date shifting for more information. Supported types: Date, DateTime.
- keep_field KeepField Response 
- Keep the field unchanged.
- paths Sequence[str]
- List of paths to FHIR fields to redact. Each path is a period-separated list where each component is either a field name or FHIR type name. All types begin with an upper case letter. For example, the resource field Patient.Address.city, which uses a string type, can be matched byPatient.Address.String. Partial matching is supported. For example,Patient.Address.citycan be matched byAddress.city(withPatientomitted). Partial matching and type matching can be combined, for examplePatient.Address.citycan be matched byAddress.String. For "choice" types (those defined in the FHIR spec with the formatfield[x]), use two separate components. For example,deceasedAge.unitis matched byDeceased.Age.unit. The following types are supported: AdministrativeGenderCode, Base64Binary, Boolean, Code, Date, DateTime, Decimal, HumanName, Id, Instant, Integer, LanguageCode, Markdown, Oid, PositiveInt, String, UnsignedInt, Uri, Uuid, Xhtml. The sub-type for HumanName (for exampleHumanName.given,HumanName.family) can be omitted.
- remove_field RemoveField Response 
- Remove the field.
- characterMask Property MapField 
- Replace the field's value with a masking character. Supported types: Code, Decimal, HumanName, Id, LanguageCode, Markdown, Oid, String, Uri, Uuid, Xhtml.
- cleanText Property MapField 
- Inspect the field's text and transform sensitive text. Configure using TextConfig. Supported types: Code, Date, DateTime, Decimal, HumanName, Id, LanguageCode, Markdown, Oid, String, Uri, Uuid, Xhtml.
- cryptoHash Property MapField 
- Replace field value with a hash of that value. Supported types: Code, Decimal, HumanName, Id, LanguageCode, Markdown, Oid, String, Uri, Uuid, Xhtml.
- dateShift Property MapField 
- Shift the date by a randomized number of days. See date shifting for more information. Supported types: Date, DateTime.
- keepField Property Map
- Keep the field unchanged.
- paths List<String>
- List of paths to FHIR fields to redact. Each path is a period-separated list where each component is either a field name or FHIR type name. All types begin with an upper case letter. For example, the resource field Patient.Address.city, which uses a string type, can be matched byPatient.Address.String. Partial matching is supported. For example,Patient.Address.citycan be matched byAddress.city(withPatientomitted). Partial matching and type matching can be combined, for examplePatient.Address.citycan be matched byAddress.String. For "choice" types (those defined in the FHIR spec with the formatfield[x]), use two separate components. For example,deceasedAge.unitis matched byDeceased.Age.unit. The following types are supported: AdministrativeGenderCode, Base64Binary, Boolean, Code, Date, DateTime, Decimal, HumanName, Id, Instant, Integer, LanguageCode, Markdown, Oid, PositiveInt, String, UnsignedInt, Uri, Uuid, Xhtml. The sub-type for HumanName (for exampleHumanName.given,HumanName.family) can be omitted.
- removeField Property Map
- Remove the field.
GoogleCloudHealthcareV1beta1DeidentifyOptionsResponse     
- CharacterMask Pulumi.Config Google Native. Healthcare. V1Beta1. Inputs. Character Mask Config Response 
- Character mask config for CharacterMaskField.
- ContextualDeid Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Contextual Deid Config Response 
- Configure contextual de-id.
- CryptoHash Pulumi.Config Google Native. Healthcare. V1Beta1. Inputs. Crypto Hash Config Response 
- Crypto hash config for CharacterMaskField.
- DateShift Pulumi.Config Google Native. Healthcare. V1Beta1. Inputs. Date Shift Config Response 
- Date shifting config for CharacterMaskField.
- KeepExtensions Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Keep Extensions Config Response 
- Configure keeping extensions by default.
- CharacterMask CharacterConfig Mask Config Response 
- Character mask config for CharacterMaskField.
- ContextualDeid ContextualDeid Config Response 
- Configure contextual de-id.
- CryptoHash CryptoConfig Hash Config Response 
- Crypto hash config for CharacterMaskField.
- DateShift DateConfig Shift Config Response 
- Date shifting config for CharacterMaskField.
- KeepExtensions KeepExtensions Config Response 
- Configure keeping extensions by default.
- characterMask CharacterConfig Mask Config Response 
- Character mask config for CharacterMaskField.
- contextualDeid ContextualDeid Config Response 
- Configure contextual de-id.
- cryptoHash CryptoConfig Hash Config Response 
- Crypto hash config for CharacterMaskField.
- dateShift DateConfig Shift Config Response 
- Date shifting config for CharacterMaskField.
- keepExtensions KeepExtensions Config Response 
- Configure keeping extensions by default.
- characterMask CharacterConfig Mask Config Response 
- Character mask config for CharacterMaskField.
- contextualDeid ContextualDeid Config Response 
- Configure contextual de-id.
- cryptoHash CryptoConfig Hash Config Response 
- Crypto hash config for CharacterMaskField.
- dateShift DateConfig Shift Config Response 
- Date shifting config for CharacterMaskField.
- keepExtensions KeepExtensions Config Response 
- Configure keeping extensions by default.
- character_mask_ Characterconfig Mask Config Response 
- Character mask config for CharacterMaskField.
- contextual_deid ContextualDeid Config Response 
- Configure contextual de-id.
- crypto_hash_ Cryptoconfig Hash Config Response 
- Crypto hash config for CharacterMaskField.
- date_shift_ Dateconfig Shift Config Response 
- Date shifting config for CharacterMaskField.
- keep_extensions KeepExtensions Config Response 
- Configure keeping extensions by default.
- characterMask Property MapConfig 
- Character mask config for CharacterMaskField.
- contextualDeid Property Map
- Configure contextual de-id.
- cryptoHash Property MapConfig 
- Crypto hash config for CharacterMaskField.
- dateShift Property MapConfig 
- Date shifting config for CharacterMaskField.
- keepExtensions Property Map
- Configure keeping extensions by default.
GoogleCloudHealthcareV1beta1FhirBigQueryDestinationResponse       
- DatasetUri string
- BigQuery URI to an existing dataset, up to 2000 characters long, in the format bq://projectId.bqDatasetId.
- Force bool
- Use write_dispositioninstead. Ifwrite_dispositionis specified, this parameter is ignored. force=false is equivalent to write_disposition=WRITE_EMPTY and force=true is equivalent to write_disposition=WRITE_TRUNCATE.
- SchemaConfig Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Schema Config Response 
- The configuration for the exported BigQuery schema.
- WriteDisposition string
- Determines if existing data in the destination dataset is overwritten, appended to, or not written if the tables contain data. If a write_disposition is specified, the forceparameter is ignored.
- DatasetUri string
- BigQuery URI to an existing dataset, up to 2000 characters long, in the format bq://projectId.bqDatasetId.
- Force bool
- Use write_dispositioninstead. Ifwrite_dispositionis specified, this parameter is ignored. force=false is equivalent to write_disposition=WRITE_EMPTY and force=true is equivalent to write_disposition=WRITE_TRUNCATE.
- SchemaConfig SchemaConfig Response 
- The configuration for the exported BigQuery schema.
- WriteDisposition string
- Determines if existing data in the destination dataset is overwritten, appended to, or not written if the tables contain data. If a write_disposition is specified, the forceparameter is ignored.
- datasetUri String
- BigQuery URI to an existing dataset, up to 2000 characters long, in the format bq://projectId.bqDatasetId.
- force Boolean
- Use write_dispositioninstead. Ifwrite_dispositionis specified, this parameter is ignored. force=false is equivalent to write_disposition=WRITE_EMPTY and force=true is equivalent to write_disposition=WRITE_TRUNCATE.
- schemaConfig SchemaConfig Response 
- The configuration for the exported BigQuery schema.
- writeDisposition String
- Determines if existing data in the destination dataset is overwritten, appended to, or not written if the tables contain data. If a write_disposition is specified, the forceparameter is ignored.
- datasetUri string
- BigQuery URI to an existing dataset, up to 2000 characters long, in the format bq://projectId.bqDatasetId.
- force boolean
- Use write_dispositioninstead. Ifwrite_dispositionis specified, this parameter is ignored. force=false is equivalent to write_disposition=WRITE_EMPTY and force=true is equivalent to write_disposition=WRITE_TRUNCATE.
- schemaConfig SchemaConfig Response 
- The configuration for the exported BigQuery schema.
- writeDisposition string
- Determines if existing data in the destination dataset is overwritten, appended to, or not written if the tables contain data. If a write_disposition is specified, the forceparameter is ignored.
- dataset_uri str
- BigQuery URI to an existing dataset, up to 2000 characters long, in the format bq://projectId.bqDatasetId.
- force bool
- Use write_dispositioninstead. Ifwrite_dispositionis specified, this parameter is ignored. force=false is equivalent to write_disposition=WRITE_EMPTY and force=true is equivalent to write_disposition=WRITE_TRUNCATE.
- schema_config SchemaConfig Response 
- The configuration for the exported BigQuery schema.
- write_disposition str
- Determines if existing data in the destination dataset is overwritten, appended to, or not written if the tables contain data. If a write_disposition is specified, the forceparameter is ignored.
- datasetUri String
- BigQuery URI to an existing dataset, up to 2000 characters long, in the format bq://projectId.bqDatasetId.
- force Boolean
- Use write_dispositioninstead. Ifwrite_dispositionis specified, this parameter is ignored. force=false is equivalent to write_disposition=WRITE_EMPTY and force=true is equivalent to write_disposition=WRITE_TRUNCATE.
- schemaConfig Property Map
- The configuration for the exported BigQuery schema.
- writeDisposition String
- Determines if existing data in the destination dataset is overwritten, appended to, or not written if the tables contain data. If a write_disposition is specified, the forceparameter is ignored.
ImageConfigResponse  
- AdditionalInfo List<string>Types 
- Additional InfoTypes to redact in the images in addition to those used by text_redaction_mode. Can only be used whentext_redaction_modeis set toREDACT_SENSITIVE_TEXT,REDACT_SENSITIVE_TEXT_CLEAN_DESCRIPTORSorTEXT_REDACTION_MODE_UNSPECIFIED.
- ExcludeInfo List<string>Types 
- InfoTypes to skip redacting, overriding those used by text_redaction_mode. Can only be used whentext_redaction_modeis set toREDACT_SENSITIVE_TEXTorREDACT_SENSITIVE_TEXT_CLEAN_DESCRIPTORS.
- TextRedaction stringMode 
- Determines how to redact text from image.
- AdditionalInfo []stringTypes 
- Additional InfoTypes to redact in the images in addition to those used by text_redaction_mode. Can only be used whentext_redaction_modeis set toREDACT_SENSITIVE_TEXT,REDACT_SENSITIVE_TEXT_CLEAN_DESCRIPTORSorTEXT_REDACTION_MODE_UNSPECIFIED.
- ExcludeInfo []stringTypes 
- InfoTypes to skip redacting, overriding those used by text_redaction_mode. Can only be used whentext_redaction_modeis set toREDACT_SENSITIVE_TEXTorREDACT_SENSITIVE_TEXT_CLEAN_DESCRIPTORS.
- TextRedaction stringMode 
- Determines how to redact text from image.
- additionalInfo List<String>Types 
- Additional InfoTypes to redact in the images in addition to those used by text_redaction_mode. Can only be used whentext_redaction_modeis set toREDACT_SENSITIVE_TEXT,REDACT_SENSITIVE_TEXT_CLEAN_DESCRIPTORSorTEXT_REDACTION_MODE_UNSPECIFIED.
- excludeInfo List<String>Types 
- InfoTypes to skip redacting, overriding those used by text_redaction_mode. Can only be used whentext_redaction_modeis set toREDACT_SENSITIVE_TEXTorREDACT_SENSITIVE_TEXT_CLEAN_DESCRIPTORS.
- textRedaction StringMode 
- Determines how to redact text from image.
- additionalInfo string[]Types 
- Additional InfoTypes to redact in the images in addition to those used by text_redaction_mode. Can only be used whentext_redaction_modeis set toREDACT_SENSITIVE_TEXT,REDACT_SENSITIVE_TEXT_CLEAN_DESCRIPTORSorTEXT_REDACTION_MODE_UNSPECIFIED.
- excludeInfo string[]Types 
- InfoTypes to skip redacting, overriding those used by text_redaction_mode. Can only be used whentext_redaction_modeis set toREDACT_SENSITIVE_TEXTorREDACT_SENSITIVE_TEXT_CLEAN_DESCRIPTORS.
- textRedaction stringMode 
- Determines how to redact text from image.
- additional_info_ Sequence[str]types 
- Additional InfoTypes to redact in the images in addition to those used by text_redaction_mode. Can only be used whentext_redaction_modeis set toREDACT_SENSITIVE_TEXT,REDACT_SENSITIVE_TEXT_CLEAN_DESCRIPTORSorTEXT_REDACTION_MODE_UNSPECIFIED.
- exclude_info_ Sequence[str]types 
- InfoTypes to skip redacting, overriding those used by text_redaction_mode. Can only be used whentext_redaction_modeis set toREDACT_SENSITIVE_TEXTorREDACT_SENSITIVE_TEXT_CLEAN_DESCRIPTORS.
- text_redaction_ strmode 
- Determines how to redact text from image.
- additionalInfo List<String>Types 
- Additional InfoTypes to redact in the images in addition to those used by text_redaction_mode. Can only be used whentext_redaction_modeis set toREDACT_SENSITIVE_TEXT,REDACT_SENSITIVE_TEXT_CLEAN_DESCRIPTORSorTEXT_REDACTION_MODE_UNSPECIFIED.
- excludeInfo List<String>Types 
- InfoTypes to skip redacting, overriding those used by text_redaction_mode. Can only be used whentext_redaction_modeis set toREDACT_SENSITIVE_TEXTorREDACT_SENSITIVE_TEXT_CLEAN_DESCRIPTORS.
- textRedaction StringMode 
- Determines how to redact text from image.
InfoTypeTransformationResponse   
- CharacterMask Pulumi.Config Google Native. Healthcare. V1Beta1. Inputs. Character Mask Config Response 
- Config for character mask.
- CryptoHash Pulumi.Config Google Native. Healthcare. V1Beta1. Inputs. Crypto Hash Config Response 
- Config for crypto hash.
- DateShift Pulumi.Config Google Native. Healthcare. V1Beta1. Inputs. Date Shift Config Response 
- Config for date shift.
- InfoTypes List<string>
- InfoTypesto apply this transformation to. If this is not specified, this transformation becomes the default transformation, and is used for any- info_typethat is not specified in another transformation.
- RedactConfig Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Redact Config Response 
- Config for text redaction.
- ReplaceWith Pulumi.Info Type Config Google Native. Healthcare. V1Beta1. Inputs. Replace With Info Type Config Response 
- Config for replace with InfoType.
- CharacterMask CharacterConfig Mask Config Response 
- Config for character mask.
- CryptoHash CryptoConfig Hash Config Response 
- Config for crypto hash.
- DateShift DateConfig Shift Config Response 
- Config for date shift.
- InfoTypes []string
- InfoTypesto apply this transformation to. If this is not specified, this transformation becomes the default transformation, and is used for any- info_typethat is not specified in another transformation.
- RedactConfig RedactConfig Response 
- Config for text redaction.
- ReplaceWith ReplaceInfo Type Config With Info Type Config Response 
- Config for replace with InfoType.
- characterMask CharacterConfig Mask Config Response 
- Config for character mask.
- cryptoHash CryptoConfig Hash Config Response 
- Config for crypto hash.
- dateShift DateConfig Shift Config Response 
- Config for date shift.
- infoTypes List<String>
- InfoTypesto apply this transformation to. If this is not specified, this transformation becomes the default transformation, and is used for any- info_typethat is not specified in another transformation.
- redactConfig RedactConfig Response 
- Config for text redaction.
- replaceWith ReplaceInfo Type Config With Info Type Config Response 
- Config for replace with InfoType.
- characterMask CharacterConfig Mask Config Response 
- Config for character mask.
- cryptoHash CryptoConfig Hash Config Response 
- Config for crypto hash.
- dateShift DateConfig Shift Config Response 
- Config for date shift.
- infoTypes string[]
- InfoTypesto apply this transformation to. If this is not specified, this transformation becomes the default transformation, and is used for any- info_typethat is not specified in another transformation.
- redactConfig RedactConfig Response 
- Config for text redaction.
- replaceWith ReplaceInfo Type Config With Info Type Config Response 
- Config for replace with InfoType.
- character_mask_ Characterconfig Mask Config Response 
- Config for character mask.
- crypto_hash_ Cryptoconfig Hash Config Response 
- Config for crypto hash.
- date_shift_ Dateconfig Shift Config Response 
- Config for date shift.
- info_types Sequence[str]
- InfoTypesto apply this transformation to. If this is not specified, this transformation becomes the default transformation, and is used for any- info_typethat is not specified in another transformation.
- redact_config RedactConfig Response 
- Config for text redaction.
- replace_with_ Replaceinfo_ type_ config With Info Type Config Response 
- Config for replace with InfoType.
- characterMask Property MapConfig 
- Config for character mask.
- cryptoHash Property MapConfig 
- Config for crypto hash.
- dateShift Property MapConfig 
- Config for date shift.
- infoTypes List<String>
- InfoTypesto apply this transformation to. If this is not specified, this transformation becomes the default transformation, and is used for any- info_typethat is not specified in another transformation.
- redactConfig Property Map
- Config for text redaction.
- replaceWith Property MapInfo Type Config 
- Config for replace with InfoType.
KmsWrappedCryptoKeyResponse    
- CryptoKey string
- The resource name of the KMS CryptoKey to use for unwrapping. For example, projects/{project_id}/locations/{location_id}/keyRings/{keyring}/cryptoKeys/{key}.
- WrappedKey string
- The wrapped data crypto key.
- CryptoKey string
- The resource name of the KMS CryptoKey to use for unwrapping. For example, projects/{project_id}/locations/{location_id}/keyRings/{keyring}/cryptoKeys/{key}.
- WrappedKey string
- The wrapped data crypto key.
- cryptoKey String
- The resource name of the KMS CryptoKey to use for unwrapping. For example, projects/{project_id}/locations/{location_id}/keyRings/{keyring}/cryptoKeys/{key}.
- wrappedKey String
- The wrapped data crypto key.
- cryptoKey string
- The resource name of the KMS CryptoKey to use for unwrapping. For example, projects/{project_id}/locations/{location_id}/keyRings/{keyring}/cryptoKeys/{key}.
- wrappedKey string
- The wrapped data crypto key.
- crypto_key str
- The resource name of the KMS CryptoKey to use for unwrapping. For example, projects/{project_id}/locations/{location_id}/keyRings/{keyring}/cryptoKeys/{key}.
- wrapped_key str
- The wrapped data crypto key.
- cryptoKey String
- The resource name of the KMS CryptoKey to use for unwrapping. For example, projects/{project_id}/locations/{location_id}/keyRings/{keyring}/cryptoKeys/{key}.
- wrappedKey String
- The wrapped data crypto key.
NotificationConfigResponse  
- PubsubTopic string
- The Pub/Sub topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging (see Viewing error logs in Cloud Logging). If the number of errors exceeds a certain rate, some aren't submitted. Note that not all operations trigger notifications, see Configuring Pub/Sub notifications for specific details.
- SendFor boolBulk Import 
- Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
- PubsubTopic string
- The Pub/Sub topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging (see Viewing error logs in Cloud Logging). If the number of errors exceeds a certain rate, some aren't submitted. Note that not all operations trigger notifications, see Configuring Pub/Sub notifications for specific details.
- SendFor boolBulk Import 
- Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
- pubsubTopic String
- The Pub/Sub topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging (see Viewing error logs in Cloud Logging). If the number of errors exceeds a certain rate, some aren't submitted. Note that not all operations trigger notifications, see Configuring Pub/Sub notifications for specific details.
- sendFor BooleanBulk Import 
- Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
- pubsubTopic string
- The Pub/Sub topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging (see Viewing error logs in Cloud Logging). If the number of errors exceeds a certain rate, some aren't submitted. Note that not all operations trigger notifications, see Configuring Pub/Sub notifications for specific details.
- sendFor booleanBulk Import 
- Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
- pubsub_topic str
- The Pub/Sub topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging (see Viewing error logs in Cloud Logging). If the number of errors exceeds a certain rate, some aren't submitted. Note that not all operations trigger notifications, see Configuring Pub/Sub notifications for specific details.
- send_for_ boolbulk_ import 
- Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
- pubsubTopic String
- The Pub/Sub topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging (see Viewing error logs in Cloud Logging). If the number of errors exceeds a certain rate, some aren't submitted. Note that not all operations trigger notifications, see Configuring Pub/Sub notifications for specific details.
- sendFor BooleanBulk Import 
- Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
OptionsResponse 
- CleanDescriptors Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Clean Descriptors Option Response 
- Set Clean Descriptors Option.
- CleanImage Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Image Config Response 
- Apply Action.clean_imagetoPixelDataas configured.
- PrimaryIds string
- Set ActionforStudyInstanceUID,SeriesInstanceUID,SOPInstanceUID, andMediaStorageSOPInstanceUID.
- CleanDescriptors CleanDescriptors Option Response 
- Set Clean Descriptors Option.
- CleanImage ImageConfig Response 
- Apply Action.clean_imagetoPixelDataas configured.
- PrimaryIds string
- Set ActionforStudyInstanceUID,SeriesInstanceUID,SOPInstanceUID, andMediaStorageSOPInstanceUID.
- cleanDescriptors CleanDescriptors Option Response 
- Set Clean Descriptors Option.
- cleanImage ImageConfig Response 
- Apply Action.clean_imagetoPixelDataas configured.
- primaryIds String
- Set ActionforStudyInstanceUID,SeriesInstanceUID,SOPInstanceUID, andMediaStorageSOPInstanceUID.
- cleanDescriptors CleanDescriptors Option Response 
- Set Clean Descriptors Option.
- cleanImage ImageConfig Response 
- Apply Action.clean_imagetoPixelDataas configured.
- primaryIds string
- Set ActionforStudyInstanceUID,SeriesInstanceUID,SOPInstanceUID, andMediaStorageSOPInstanceUID.
- clean_descriptors CleanDescriptors Option Response 
- Set Clean Descriptors Option.
- clean_image ImageConfig Response 
- Apply Action.clean_imagetoPixelDataas configured.
- primary_ids str
- Set ActionforStudyInstanceUID,SeriesInstanceUID,SOPInstanceUID, andMediaStorageSOPInstanceUID.
- cleanDescriptors Property Map
- Set Clean Descriptors Option.
- cleanImage Property Map
- Apply Action.clean_imagetoPixelDataas configured.
- primaryIds String
- Set ActionforStudyInstanceUID,SeriesInstanceUID,SOPInstanceUID, andMediaStorageSOPInstanceUID.
SchemaConfigResponse  
- LastUpdated Pulumi.Partition Config Google Native. Healthcare. V1Beta1. Inputs. Time Partitioning Response 
- The configuration for exported BigQuery tables to be partitioned by FHIR resource's last updated time column.
- RecursiveStructure stringDepth 
- The depth for all recursive structures in the output analytics schema. For example, conceptin the CodeSystem resource is a recursive structure; when the depth is 2, the CodeSystem table will have a column calledconcept.conceptbut notconcept.concept.concept. If not specified or set to 0, the server will use the default value 2. The maximum depth allowed is 5.
- SchemaType string
- Specifies the output schema type. Schema type is required.
- LastUpdated TimePartition Config Partitioning Response 
- The configuration for exported BigQuery tables to be partitioned by FHIR resource's last updated time column.
- RecursiveStructure stringDepth 
- The depth for all recursive structures in the output analytics schema. For example, conceptin the CodeSystem resource is a recursive structure; when the depth is 2, the CodeSystem table will have a column calledconcept.conceptbut notconcept.concept.concept. If not specified or set to 0, the server will use the default value 2. The maximum depth allowed is 5.
- SchemaType string
- Specifies the output schema type. Schema type is required.
- lastUpdated TimePartition Config Partitioning Response 
- The configuration for exported BigQuery tables to be partitioned by FHIR resource's last updated time column.
- recursiveStructure StringDepth 
- The depth for all recursive structures in the output analytics schema. For example, conceptin the CodeSystem resource is a recursive structure; when the depth is 2, the CodeSystem table will have a column calledconcept.conceptbut notconcept.concept.concept. If not specified or set to 0, the server will use the default value 2. The maximum depth allowed is 5.
- schemaType String
- Specifies the output schema type. Schema type is required.
- lastUpdated TimePartition Config Partitioning Response 
- The configuration for exported BigQuery tables to be partitioned by FHIR resource's last updated time column.
- recursiveStructure stringDepth 
- The depth for all recursive structures in the output analytics schema. For example, conceptin the CodeSystem resource is a recursive structure; when the depth is 2, the CodeSystem table will have a column calledconcept.conceptbut notconcept.concept.concept. If not specified or set to 0, the server will use the default value 2. The maximum depth allowed is 5.
- schemaType string
- Specifies the output schema type. Schema type is required.
- last_updated_ Timepartition_ config Partitioning Response 
- The configuration for exported BigQuery tables to be partitioned by FHIR resource's last updated time column.
- recursive_structure_ strdepth 
- The depth for all recursive structures in the output analytics schema. For example, conceptin the CodeSystem resource is a recursive structure; when the depth is 2, the CodeSystem table will have a column calledconcept.conceptbut notconcept.concept.concept. If not specified or set to 0, the server will use the default value 2. The maximum depth allowed is 5.
- schema_type str
- Specifies the output schema type. Schema type is required.
- lastUpdated Property MapPartition Config 
- The configuration for exported BigQuery tables to be partitioned by FHIR resource's last updated time column.
- recursiveStructure StringDepth 
- The depth for all recursive structures in the output analytics schema. For example, conceptin the CodeSystem resource is a recursive structure; when the depth is 2, the CodeSystem table will have a column calledconcept.conceptbut notconcept.concept.concept. If not specified or set to 0, the server will use the default value 2. The maximum depth allowed is 5.
- schemaType String
- Specifies the output schema type. Schema type is required.
SearchConfigResponse  
- SearchParameters List<Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Search Parameter Response> 
- A list of search parameters in this FHIR store that are used to configure this FHIR store.
- SearchParameters []SearchParameter Response 
- A list of search parameters in this FHIR store that are used to configure this FHIR store.
- searchParameters List<SearchParameter Response> 
- A list of search parameters in this FHIR store that are used to configure this FHIR store.
- searchParameters SearchParameter Response[] 
- A list of search parameters in this FHIR store that are used to configure this FHIR store.
- search_parameters Sequence[SearchParameter Response] 
- A list of search parameters in this FHIR store that are used to configure this FHIR store.
- searchParameters List<Property Map>
- A list of search parameters in this FHIR store that are used to configure this FHIR store.
SearchParameterResponse  
- CanonicalUrl string
- The canonical url of the search parameter resource.
- Parameter string
- The versioned name of the search parameter resource. The format is projects/{project-id}/locations/{location}/datasets/{dataset-id}/fhirStores/{fhirStore-id}/fhir/SearchParameter/{resource-id}/_history/{version-id} For fhir stores with disable_resource_versioning=true, the format is projects/{project-id}/locations/{location}/datasets/{dataset-id}/fhirStores/{fhirStore-id}/fhir/SearchParameter/{resource-id}/
- CanonicalUrl string
- The canonical url of the search parameter resource.
- Parameter string
- The versioned name of the search parameter resource. The format is projects/{project-id}/locations/{location}/datasets/{dataset-id}/fhirStores/{fhirStore-id}/fhir/SearchParameter/{resource-id}/_history/{version-id} For fhir stores with disable_resource_versioning=true, the format is projects/{project-id}/locations/{location}/datasets/{dataset-id}/fhirStores/{fhirStore-id}/fhir/SearchParameter/{resource-id}/
- canonicalUrl String
- The canonical url of the search parameter resource.
- parameter String
- The versioned name of the search parameter resource. The format is projects/{project-id}/locations/{location}/datasets/{dataset-id}/fhirStores/{fhirStore-id}/fhir/SearchParameter/{resource-id}/_history/{version-id} For fhir stores with disable_resource_versioning=true, the format is projects/{project-id}/locations/{location}/datasets/{dataset-id}/fhirStores/{fhirStore-id}/fhir/SearchParameter/{resource-id}/
- canonicalUrl string
- The canonical url of the search parameter resource.
- parameter string
- The versioned name of the search parameter resource. The format is projects/{project-id}/locations/{location}/datasets/{dataset-id}/fhirStores/{fhirStore-id}/fhir/SearchParameter/{resource-id}/_history/{version-id} For fhir stores with disable_resource_versioning=true, the format is projects/{project-id}/locations/{location}/datasets/{dataset-id}/fhirStores/{fhirStore-id}/fhir/SearchParameter/{resource-id}/
- canonical_url str
- The canonical url of the search parameter resource.
- parameter str
- The versioned name of the search parameter resource. The format is projects/{project-id}/locations/{location}/datasets/{dataset-id}/fhirStores/{fhirStore-id}/fhir/SearchParameter/{resource-id}/_history/{version-id} For fhir stores with disable_resource_versioning=true, the format is projects/{project-id}/locations/{location}/datasets/{dataset-id}/fhirStores/{fhirStore-id}/fhir/SearchParameter/{resource-id}/
- canonicalUrl String
- The canonical url of the search parameter resource.
- parameter String
- The versioned name of the search parameter resource. The format is projects/{project-id}/locations/{location}/datasets/{dataset-id}/fhirStores/{fhirStore-id}/fhir/SearchParameter/{resource-id}/_history/{version-id} For fhir stores with disable_resource_versioning=true, the format is projects/{project-id}/locations/{location}/datasets/{dataset-id}/fhirStores/{fhirStore-id}/fhir/SearchParameter/{resource-id}/
StreamConfigResponse  
- BigqueryDestination Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Google Cloud Healthcare V1beta1Fhir Big Query Destination Response 
- The destination BigQuery structure that contains both the dataset location and corresponding schema config. The output is organized in one table per resource type. The server reuses the existing tables (if any) that are named after the resource types, e.g. "Patient", "Observation". When there is no existing table for a given resource type, the server attempts to create one. When a table schema doesn't align with the schema config, either because of existing incompatible schema or out of band incompatible modification, the server does not stream in new data. One resolution in this case is to delete the incompatible table and let the server recreate one, though the newly created table only contains data after the table recreation. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any resource mutation that generates more than 1 MB of BigQuery data will not be streamed. Results are written to BigQuery tables according to the parameters in BigQueryDestination.WriteDisposition. Different versions of the same resource are distinguishable by the meta.versionId and meta.lastUpdated columns. The operation (CREATE/UPDATE/DELETE) that results in the new version is recorded in the meta.tag. The tables contain all historical resource versions since streaming was enabled. For query convenience, the server also creates one view per table of the same name containing only the current resource version. The streamed data in the BigQuery dataset is not guaranteed to be completely unique. The combination of the id and meta.versionId columns should ideally identify a single unique row. But in rare cases, duplicates may exist. At query time, users may use the SQL select statement to keep only one of the duplicate rows given an id and meta.versionId pair. Alternatively, the server created view mentioned above also filters out duplicates. If a resource mutation cannot be streamed to BigQuery, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
- DeidentifiedStore Pulumi.Destination Google Native. Healthcare. V1Beta1. Inputs. Deidentified Store Destination Response 
- The destination FHIR store for de-identified resources. After this field is added, all subsequent creates/updates/patches to the source store will be de-identified using the provided configuration and applied to the destination store. Importing resources to the source store will not trigger the streaming. If the source store already contains resources when this option is enabled, those resources will not be copied to the destination store unless they are subsequently updated. This may result in invalid references in the destination store. Before adding this config, you must grant the healthcare.fhirResources.update permission on the destination store to your project's Cloud Healthcare Service Agent service account. The destination store must set enable_update_create to true. The destination store must have disable_referential_integrity set to true. If a resource cannot be de-identified, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
- ResourceTypes List<string>
- Supply a FHIR resource type (such as "Patient" or "Observation"). See https://www.hl7.org/fhir/valueset-resource-types.html for a list of all FHIR resource types. The server treats an empty list as an intent to stream all the supported resource types in this FHIR store.
- BigqueryDestination GoogleCloud Healthcare V1beta1Fhir Big Query Destination Response 
- The destination BigQuery structure that contains both the dataset location and corresponding schema config. The output is organized in one table per resource type. The server reuses the existing tables (if any) that are named after the resource types, e.g. "Patient", "Observation". When there is no existing table for a given resource type, the server attempts to create one. When a table schema doesn't align with the schema config, either because of existing incompatible schema or out of band incompatible modification, the server does not stream in new data. One resolution in this case is to delete the incompatible table and let the server recreate one, though the newly created table only contains data after the table recreation. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any resource mutation that generates more than 1 MB of BigQuery data will not be streamed. Results are written to BigQuery tables according to the parameters in BigQueryDestination.WriteDisposition. Different versions of the same resource are distinguishable by the meta.versionId and meta.lastUpdated columns. The operation (CREATE/UPDATE/DELETE) that results in the new version is recorded in the meta.tag. The tables contain all historical resource versions since streaming was enabled. For query convenience, the server also creates one view per table of the same name containing only the current resource version. The streamed data in the BigQuery dataset is not guaranteed to be completely unique. The combination of the id and meta.versionId columns should ideally identify a single unique row. But in rare cases, duplicates may exist. At query time, users may use the SQL select statement to keep only one of the duplicate rows given an id and meta.versionId pair. Alternatively, the server created view mentioned above also filters out duplicates. If a resource mutation cannot be streamed to BigQuery, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
- DeidentifiedStore DeidentifiedDestination Store Destination Response 
- The destination FHIR store for de-identified resources. After this field is added, all subsequent creates/updates/patches to the source store will be de-identified using the provided configuration and applied to the destination store. Importing resources to the source store will not trigger the streaming. If the source store already contains resources when this option is enabled, those resources will not be copied to the destination store unless they are subsequently updated. This may result in invalid references in the destination store. Before adding this config, you must grant the healthcare.fhirResources.update permission on the destination store to your project's Cloud Healthcare Service Agent service account. The destination store must set enable_update_create to true. The destination store must have disable_referential_integrity set to true. If a resource cannot be de-identified, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
- ResourceTypes []string
- Supply a FHIR resource type (such as "Patient" or "Observation"). See https://www.hl7.org/fhir/valueset-resource-types.html for a list of all FHIR resource types. The server treats an empty list as an intent to stream all the supported resource types in this FHIR store.
- bigqueryDestination GoogleCloud Healthcare V1beta1Fhir Big Query Destination Response 
- The destination BigQuery structure that contains both the dataset location and corresponding schema config. The output is organized in one table per resource type. The server reuses the existing tables (if any) that are named after the resource types, e.g. "Patient", "Observation". When there is no existing table for a given resource type, the server attempts to create one. When a table schema doesn't align with the schema config, either because of existing incompatible schema or out of band incompatible modification, the server does not stream in new data. One resolution in this case is to delete the incompatible table and let the server recreate one, though the newly created table only contains data after the table recreation. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any resource mutation that generates more than 1 MB of BigQuery data will not be streamed. Results are written to BigQuery tables according to the parameters in BigQueryDestination.WriteDisposition. Different versions of the same resource are distinguishable by the meta.versionId and meta.lastUpdated columns. The operation (CREATE/UPDATE/DELETE) that results in the new version is recorded in the meta.tag. The tables contain all historical resource versions since streaming was enabled. For query convenience, the server also creates one view per table of the same name containing only the current resource version. The streamed data in the BigQuery dataset is not guaranteed to be completely unique. The combination of the id and meta.versionId columns should ideally identify a single unique row. But in rare cases, duplicates may exist. At query time, users may use the SQL select statement to keep only one of the duplicate rows given an id and meta.versionId pair. Alternatively, the server created view mentioned above also filters out duplicates. If a resource mutation cannot be streamed to BigQuery, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
- deidentifiedStore DeidentifiedDestination Store Destination Response 
- The destination FHIR store for de-identified resources. After this field is added, all subsequent creates/updates/patches to the source store will be de-identified using the provided configuration and applied to the destination store. Importing resources to the source store will not trigger the streaming. If the source store already contains resources when this option is enabled, those resources will not be copied to the destination store unless they are subsequently updated. This may result in invalid references in the destination store. Before adding this config, you must grant the healthcare.fhirResources.update permission on the destination store to your project's Cloud Healthcare Service Agent service account. The destination store must set enable_update_create to true. The destination store must have disable_referential_integrity set to true. If a resource cannot be de-identified, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
- resourceTypes List<String>
- Supply a FHIR resource type (such as "Patient" or "Observation"). See https://www.hl7.org/fhir/valueset-resource-types.html for a list of all FHIR resource types. The server treats an empty list as an intent to stream all the supported resource types in this FHIR store.
- bigqueryDestination GoogleCloud Healthcare V1beta1Fhir Big Query Destination Response 
- The destination BigQuery structure that contains both the dataset location and corresponding schema config. The output is organized in one table per resource type. The server reuses the existing tables (if any) that are named after the resource types, e.g. "Patient", "Observation". When there is no existing table for a given resource type, the server attempts to create one. When a table schema doesn't align with the schema config, either because of existing incompatible schema or out of band incompatible modification, the server does not stream in new data. One resolution in this case is to delete the incompatible table and let the server recreate one, though the newly created table only contains data after the table recreation. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any resource mutation that generates more than 1 MB of BigQuery data will not be streamed. Results are written to BigQuery tables according to the parameters in BigQueryDestination.WriteDisposition. Different versions of the same resource are distinguishable by the meta.versionId and meta.lastUpdated columns. The operation (CREATE/UPDATE/DELETE) that results in the new version is recorded in the meta.tag. The tables contain all historical resource versions since streaming was enabled. For query convenience, the server also creates one view per table of the same name containing only the current resource version. The streamed data in the BigQuery dataset is not guaranteed to be completely unique. The combination of the id and meta.versionId columns should ideally identify a single unique row. But in rare cases, duplicates may exist. At query time, users may use the SQL select statement to keep only one of the duplicate rows given an id and meta.versionId pair. Alternatively, the server created view mentioned above also filters out duplicates. If a resource mutation cannot be streamed to BigQuery, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
- deidentifiedStore DeidentifiedDestination Store Destination Response 
- The destination FHIR store for de-identified resources. After this field is added, all subsequent creates/updates/patches to the source store will be de-identified using the provided configuration and applied to the destination store. Importing resources to the source store will not trigger the streaming. If the source store already contains resources when this option is enabled, those resources will not be copied to the destination store unless they are subsequently updated. This may result in invalid references in the destination store. Before adding this config, you must grant the healthcare.fhirResources.update permission on the destination store to your project's Cloud Healthcare Service Agent service account. The destination store must set enable_update_create to true. The destination store must have disable_referential_integrity set to true. If a resource cannot be de-identified, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
- resourceTypes string[]
- Supply a FHIR resource type (such as "Patient" or "Observation"). See https://www.hl7.org/fhir/valueset-resource-types.html for a list of all FHIR resource types. The server treats an empty list as an intent to stream all the supported resource types in this FHIR store.
- bigquery_destination GoogleCloud Healthcare V1beta1Fhir Big Query Destination Response 
- The destination BigQuery structure that contains both the dataset location and corresponding schema config. The output is organized in one table per resource type. The server reuses the existing tables (if any) that are named after the resource types, e.g. "Patient", "Observation". When there is no existing table for a given resource type, the server attempts to create one. When a table schema doesn't align with the schema config, either because of existing incompatible schema or out of band incompatible modification, the server does not stream in new data. One resolution in this case is to delete the incompatible table and let the server recreate one, though the newly created table only contains data after the table recreation. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any resource mutation that generates more than 1 MB of BigQuery data will not be streamed. Results are written to BigQuery tables according to the parameters in BigQueryDestination.WriteDisposition. Different versions of the same resource are distinguishable by the meta.versionId and meta.lastUpdated columns. The operation (CREATE/UPDATE/DELETE) that results in the new version is recorded in the meta.tag. The tables contain all historical resource versions since streaming was enabled. For query convenience, the server also creates one view per table of the same name containing only the current resource version. The streamed data in the BigQuery dataset is not guaranteed to be completely unique. The combination of the id and meta.versionId columns should ideally identify a single unique row. But in rare cases, duplicates may exist. At query time, users may use the SQL select statement to keep only one of the duplicate rows given an id and meta.versionId pair. Alternatively, the server created view mentioned above also filters out duplicates. If a resource mutation cannot be streamed to BigQuery, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
- deidentified_store_ Deidentifieddestination Store Destination Response 
- The destination FHIR store for de-identified resources. After this field is added, all subsequent creates/updates/patches to the source store will be de-identified using the provided configuration and applied to the destination store. Importing resources to the source store will not trigger the streaming. If the source store already contains resources when this option is enabled, those resources will not be copied to the destination store unless they are subsequently updated. This may result in invalid references in the destination store. Before adding this config, you must grant the healthcare.fhirResources.update permission on the destination store to your project's Cloud Healthcare Service Agent service account. The destination store must set enable_update_create to true. The destination store must have disable_referential_integrity set to true. If a resource cannot be de-identified, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
- resource_types Sequence[str]
- Supply a FHIR resource type (such as "Patient" or "Observation"). See https://www.hl7.org/fhir/valueset-resource-types.html for a list of all FHIR resource types. The server treats an empty list as an intent to stream all the supported resource types in this FHIR store.
- bigqueryDestination Property Map
- The destination BigQuery structure that contains both the dataset location and corresponding schema config. The output is organized in one table per resource type. The server reuses the existing tables (if any) that are named after the resource types, e.g. "Patient", "Observation". When there is no existing table for a given resource type, the server attempts to create one. When a table schema doesn't align with the schema config, either because of existing incompatible schema or out of band incompatible modification, the server does not stream in new data. One resolution in this case is to delete the incompatible table and let the server recreate one, though the newly created table only contains data after the table recreation. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any resource mutation that generates more than 1 MB of BigQuery data will not be streamed. Results are written to BigQuery tables according to the parameters in BigQueryDestination.WriteDisposition. Different versions of the same resource are distinguishable by the meta.versionId and meta.lastUpdated columns. The operation (CREATE/UPDATE/DELETE) that results in the new version is recorded in the meta.tag. The tables contain all historical resource versions since streaming was enabled. For query convenience, the server also creates one view per table of the same name containing only the current resource version. The streamed data in the BigQuery dataset is not guaranteed to be completely unique. The combination of the id and meta.versionId columns should ideally identify a single unique row. But in rare cases, duplicates may exist. At query time, users may use the SQL select statement to keep only one of the duplicate rows given an id and meta.versionId pair. Alternatively, the server created view mentioned above also filters out duplicates. If a resource mutation cannot be streamed to BigQuery, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
- deidentifiedStore Property MapDestination 
- The destination FHIR store for de-identified resources. After this field is added, all subsequent creates/updates/patches to the source store will be de-identified using the provided configuration and applied to the destination store. Importing resources to the source store will not trigger the streaming. If the source store already contains resources when this option is enabled, those resources will not be copied to the destination store unless they are subsequently updated. This may result in invalid references in the destination store. Before adding this config, you must grant the healthcare.fhirResources.update permission on the destination store to your project's Cloud Healthcare Service Agent service account. The destination store must set enable_update_create to true. The destination store must have disable_referential_integrity set to true. If a resource cannot be de-identified, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
- resourceTypes List<String>
- Supply a FHIR resource type (such as "Patient" or "Observation"). See https://www.hl7.org/fhir/valueset-resource-types.html for a list of all FHIR resource types. The server treats an empty list as an intent to stream all the supported resource types in this FHIR store.
TagFilterListResponse   
- List<string>
- Tags to be filtered. Tags must be DICOM Data Elements, File Meta Elements, or Directory Structuring Elements, as defined at: http://dicom.nema.org/medical/dicom/current/output/html/part06.html#table_6-1,. They may be provided by "Keyword" or "Tag". For example, "PatientID", "00100010".
- []string
- Tags to be filtered. Tags must be DICOM Data Elements, File Meta Elements, or Directory Structuring Elements, as defined at: http://dicom.nema.org/medical/dicom/current/output/html/part06.html#table_6-1,. They may be provided by "Keyword" or "Tag". For example, "PatientID", "00100010".
- List<String>
- Tags to be filtered. Tags must be DICOM Data Elements, File Meta Elements, or Directory Structuring Elements, as defined at: http://dicom.nema.org/medical/dicom/current/output/html/part06.html#table_6-1,. They may be provided by "Keyword" or "Tag". For example, "PatientID", "00100010".
- string[]
- Tags to be filtered. Tags must be DICOM Data Elements, File Meta Elements, or Directory Structuring Elements, as defined at: http://dicom.nema.org/medical/dicom/current/output/html/part06.html#table_6-1,. They may be provided by "Keyword" or "Tag". For example, "PatientID", "00100010".
- Sequence[str]
- Tags to be filtered. Tags must be DICOM Data Elements, File Meta Elements, or Directory Structuring Elements, as defined at: http://dicom.nema.org/medical/dicom/current/output/html/part06.html#table_6-1,. They may be provided by "Keyword" or "Tag". For example, "PatientID", "00100010".
- List<String>
- Tags to be filtered. Tags must be DICOM Data Elements, File Meta Elements, or Directory Structuring Elements, as defined at: http://dicom.nema.org/medical/dicom/current/output/html/part06.html#table_6-1,. They may be provided by "Keyword" or "Tag". For example, "PatientID", "00100010".
TextConfigResponse  
- AdditionalTransformations List<Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Info Type Transformation Response> 
- Additional transformations to apply to the detected data, overriding profile.
- ExcludeInfo List<string>Types 
- InfoTypes to skip transforming, overriding profile.
- ProfileType string
- Base profile type for text transformation.
- Transformations
List<Pulumi.Google Native. Healthcare. V1Beta1. Inputs. Info Type Transformation Response> 
- The transformations to apply to the detected data. Deprecated. Use additional_transformationsinstead.
- AdditionalTransformations []InfoType Transformation Response 
- Additional transformations to apply to the detected data, overriding profile.
- ExcludeInfo []stringTypes 
- InfoTypes to skip transforming, overriding profile.
- ProfileType string
- Base profile type for text transformation.
- Transformations
[]InfoType Transformation Response 
- The transformations to apply to the detected data. Deprecated. Use additional_transformationsinstead.
- additionalTransformations List<InfoType Transformation Response> 
- Additional transformations to apply to the detected data, overriding profile.
- excludeInfo List<String>Types 
- InfoTypes to skip transforming, overriding profile.
- profileType String
- Base profile type for text transformation.
- transformations
List<InfoType Transformation Response> 
- The transformations to apply to the detected data. Deprecated. Use additional_transformationsinstead.
- additionalTransformations InfoType Transformation Response[] 
- Additional transformations to apply to the detected data, overriding profile.
- excludeInfo string[]Types 
- InfoTypes to skip transforming, overriding profile.
- profileType string
- Base profile type for text transformation.
- transformations
InfoType Transformation Response[] 
- The transformations to apply to the detected data. Deprecated. Use additional_transformationsinstead.
- additional_transformations Sequence[InfoType Transformation Response] 
- Additional transformations to apply to the detected data, overriding profile.
- exclude_info_ Sequence[str]types 
- InfoTypes to skip transforming, overriding profile.
- profile_type str
- Base profile type for text transformation.
- transformations
Sequence[InfoType Transformation Response] 
- The transformations to apply to the detected data. Deprecated. Use additional_transformationsinstead.
- additionalTransformations List<Property Map>
- Additional transformations to apply to the detected data, overriding profile.
- excludeInfo List<String>Types 
- InfoTypes to skip transforming, overriding profile.
- profileType String
- Base profile type for text transformation.
- transformations List<Property Map>
- The transformations to apply to the detected data. Deprecated. Use additional_transformationsinstead.
TimePartitioningResponse  
- ExpirationMs string
- Number of milliseconds for which to keep the storage for a partition.
- Type string
- Type of partitioning.
- ExpirationMs string
- Number of milliseconds for which to keep the storage for a partition.
- Type string
- Type of partitioning.
- expirationMs String
- Number of milliseconds for which to keep the storage for a partition.
- type String
- Type of partitioning.
- expirationMs string
- Number of milliseconds for which to keep the storage for a partition.
- type string
- Type of partitioning.
- expiration_ms str
- Number of milliseconds for which to keep the storage for a partition.
- type str
- Type of partitioning.
- expirationMs String
- Number of milliseconds for which to keep the storage for a partition.
- type String
- Type of partitioning.
ValidationConfigResponse  
- DisableFhirpath boolValidation 
- Whether to disable FHIRPath validation for incoming resources. Set this to true to disable checking incoming resources for conformance against FHIRPath requirement defined in the FHIR specification. This property only affects resource types that do not have profiles configured for them, any rules in enabled implementation guides will still be enforced.
- DisableProfile boolValidation 
- Whether to disable profile validation for this FHIR store. Set this to true to disable checking incoming resources for conformance against StructureDefinitions in this FHIR store.
- DisableReference boolType Validation 
- Whether to disable reference type validation for incoming resources. Set this to true to disable checking incoming resources for conformance against reference type requirement defined in the FHIR specification. This property only affects resource types that do not have profiles configured for them, any rules in enabled implementation guides will still be enforced.
- DisableRequired boolField Validation 
- Whether to disable required fields validation for incoming resources. Set this to true to disable checking incoming resources for conformance against required fields requirement defined in the FHIR specification. This property only affects resource types that do not have profiles configured for them, any rules in enabled implementation guides will still be enforced.
- EnabledImplementation List<string>Guides 
- A list of ImplementationGuide URLs in this FHIR store that are used to configure the profiles to use for validation. For example, to use the US Core profiles for validation, set enabled_implementation_guidesto["http://hl7.org/fhir/us/core/ImplementationGuide/ig"]. Ifenabled_implementation_guidesis empty or omitted, then incoming resources are only required to conform to the base FHIR profiles. Otherwise, a resource must conform to at least one profile listed in theglobalproperty of one of the enabled ImplementationGuides. The Cloud Healthcare API does not currently enforce all of the rules in a StructureDefinition. The following rules are supported: - min/max - minValue/maxValue - maxLength - type - fixed[x] - pattern[x] on simple types - slicing, when using "value" as the discriminator type When a URL cannot be resolved (for example, in a type assertion), the server does not return an error.
- DisableFhirpath boolValidation 
- Whether to disable FHIRPath validation for incoming resources. Set this to true to disable checking incoming resources for conformance against FHIRPath requirement defined in the FHIR specification. This property only affects resource types that do not have profiles configured for them, any rules in enabled implementation guides will still be enforced.
- DisableProfile boolValidation 
- Whether to disable profile validation for this FHIR store. Set this to true to disable checking incoming resources for conformance against StructureDefinitions in this FHIR store.
- DisableReference boolType Validation 
- Whether to disable reference type validation for incoming resources. Set this to true to disable checking incoming resources for conformance against reference type requirement defined in the FHIR specification. This property only affects resource types that do not have profiles configured for them, any rules in enabled implementation guides will still be enforced.
- DisableRequired boolField Validation 
- Whether to disable required fields validation for incoming resources. Set this to true to disable checking incoming resources for conformance against required fields requirement defined in the FHIR specification. This property only affects resource types that do not have profiles configured for them, any rules in enabled implementation guides will still be enforced.
- EnabledImplementation []stringGuides 
- A list of ImplementationGuide URLs in this FHIR store that are used to configure the profiles to use for validation. For example, to use the US Core profiles for validation, set enabled_implementation_guidesto["http://hl7.org/fhir/us/core/ImplementationGuide/ig"]. Ifenabled_implementation_guidesis empty or omitted, then incoming resources are only required to conform to the base FHIR profiles. Otherwise, a resource must conform to at least one profile listed in theglobalproperty of one of the enabled ImplementationGuides. The Cloud Healthcare API does not currently enforce all of the rules in a StructureDefinition. The following rules are supported: - min/max - minValue/maxValue - maxLength - type - fixed[x] - pattern[x] on simple types - slicing, when using "value" as the discriminator type When a URL cannot be resolved (for example, in a type assertion), the server does not return an error.
- disableFhirpath BooleanValidation 
- Whether to disable FHIRPath validation for incoming resources. Set this to true to disable checking incoming resources for conformance against FHIRPath requirement defined in the FHIR specification. This property only affects resource types that do not have profiles configured for them, any rules in enabled implementation guides will still be enforced.
- disableProfile BooleanValidation 
- Whether to disable profile validation for this FHIR store. Set this to true to disable checking incoming resources for conformance against StructureDefinitions in this FHIR store.
- disableReference BooleanType Validation 
- Whether to disable reference type validation for incoming resources. Set this to true to disable checking incoming resources for conformance against reference type requirement defined in the FHIR specification. This property only affects resource types that do not have profiles configured for them, any rules in enabled implementation guides will still be enforced.
- disableRequired BooleanField Validation 
- Whether to disable required fields validation for incoming resources. Set this to true to disable checking incoming resources for conformance against required fields requirement defined in the FHIR specification. This property only affects resource types that do not have profiles configured for them, any rules in enabled implementation guides will still be enforced.
- enabledImplementation List<String>Guides 
- A list of ImplementationGuide URLs in this FHIR store that are used to configure the profiles to use for validation. For example, to use the US Core profiles for validation, set enabled_implementation_guidesto["http://hl7.org/fhir/us/core/ImplementationGuide/ig"]. Ifenabled_implementation_guidesis empty or omitted, then incoming resources are only required to conform to the base FHIR profiles. Otherwise, a resource must conform to at least one profile listed in theglobalproperty of one of the enabled ImplementationGuides. The Cloud Healthcare API does not currently enforce all of the rules in a StructureDefinition. The following rules are supported: - min/max - minValue/maxValue - maxLength - type - fixed[x] - pattern[x] on simple types - slicing, when using "value" as the discriminator type When a URL cannot be resolved (for example, in a type assertion), the server does not return an error.
- disableFhirpath booleanValidation 
- Whether to disable FHIRPath validation for incoming resources. Set this to true to disable checking incoming resources for conformance against FHIRPath requirement defined in the FHIR specification. This property only affects resource types that do not have profiles configured for them, any rules in enabled implementation guides will still be enforced.
- disableProfile booleanValidation 
- Whether to disable profile validation for this FHIR store. Set this to true to disable checking incoming resources for conformance against StructureDefinitions in this FHIR store.
- disableReference booleanType Validation 
- Whether to disable reference type validation for incoming resources. Set this to true to disable checking incoming resources for conformance against reference type requirement defined in the FHIR specification. This property only affects resource types that do not have profiles configured for them, any rules in enabled implementation guides will still be enforced.
- disableRequired booleanField Validation 
- Whether to disable required fields validation for incoming resources. Set this to true to disable checking incoming resources for conformance against required fields requirement defined in the FHIR specification. This property only affects resource types that do not have profiles configured for them, any rules in enabled implementation guides will still be enforced.
- enabledImplementation string[]Guides 
- A list of ImplementationGuide URLs in this FHIR store that are used to configure the profiles to use for validation. For example, to use the US Core profiles for validation, set enabled_implementation_guidesto["http://hl7.org/fhir/us/core/ImplementationGuide/ig"]. Ifenabled_implementation_guidesis empty or omitted, then incoming resources are only required to conform to the base FHIR profiles. Otherwise, a resource must conform to at least one profile listed in theglobalproperty of one of the enabled ImplementationGuides. The Cloud Healthcare API does not currently enforce all of the rules in a StructureDefinition. The following rules are supported: - min/max - minValue/maxValue - maxLength - type - fixed[x] - pattern[x] on simple types - slicing, when using "value" as the discriminator type When a URL cannot be resolved (for example, in a type assertion), the server does not return an error.
- disable_fhirpath_ boolvalidation 
- Whether to disable FHIRPath validation for incoming resources. Set this to true to disable checking incoming resources for conformance against FHIRPath requirement defined in the FHIR specification. This property only affects resource types that do not have profiles configured for them, any rules in enabled implementation guides will still be enforced.
- disable_profile_ boolvalidation 
- Whether to disable profile validation for this FHIR store. Set this to true to disable checking incoming resources for conformance against StructureDefinitions in this FHIR store.
- disable_reference_ booltype_ validation 
- Whether to disable reference type validation for incoming resources. Set this to true to disable checking incoming resources for conformance against reference type requirement defined in the FHIR specification. This property only affects resource types that do not have profiles configured for them, any rules in enabled implementation guides will still be enforced.
- disable_required_ boolfield_ validation 
- Whether to disable required fields validation for incoming resources. Set this to true to disable checking incoming resources for conformance against required fields requirement defined in the FHIR specification. This property only affects resource types that do not have profiles configured for them, any rules in enabled implementation guides will still be enforced.
- enabled_implementation_ Sequence[str]guides 
- A list of ImplementationGuide URLs in this FHIR store that are used to configure the profiles to use for validation. For example, to use the US Core profiles for validation, set enabled_implementation_guidesto["http://hl7.org/fhir/us/core/ImplementationGuide/ig"]. Ifenabled_implementation_guidesis empty or omitted, then incoming resources are only required to conform to the base FHIR profiles. Otherwise, a resource must conform to at least one profile listed in theglobalproperty of one of the enabled ImplementationGuides. The Cloud Healthcare API does not currently enforce all of the rules in a StructureDefinition. The following rules are supported: - min/max - minValue/maxValue - maxLength - type - fixed[x] - pattern[x] on simple types - slicing, when using "value" as the discriminator type When a URL cannot be resolved (for example, in a type assertion), the server does not return an error.
- disableFhirpath BooleanValidation 
- Whether to disable FHIRPath validation for incoming resources. Set this to true to disable checking incoming resources for conformance against FHIRPath requirement defined in the FHIR specification. This property only affects resource types that do not have profiles configured for them, any rules in enabled implementation guides will still be enforced.
- disableProfile BooleanValidation 
- Whether to disable profile validation for this FHIR store. Set this to true to disable checking incoming resources for conformance against StructureDefinitions in this FHIR store.
- disableReference BooleanType Validation 
- Whether to disable reference type validation for incoming resources. Set this to true to disable checking incoming resources for conformance against reference type requirement defined in the FHIR specification. This property only affects resource types that do not have profiles configured for them, any rules in enabled implementation guides will still be enforced.
- disableRequired BooleanField Validation 
- Whether to disable required fields validation for incoming resources. Set this to true to disable checking incoming resources for conformance against required fields requirement defined in the FHIR specification. This property only affects resource types that do not have profiles configured for them, any rules in enabled implementation guides will still be enforced.
- enabledImplementation List<String>Guides 
- A list of ImplementationGuide URLs in this FHIR store that are used to configure the profiles to use for validation. For example, to use the US Core profiles for validation, set enabled_implementation_guidesto["http://hl7.org/fhir/us/core/ImplementationGuide/ig"]. Ifenabled_implementation_guidesis empty or omitted, then incoming resources are only required to conform to the base FHIR profiles. Otherwise, a resource must conform to at least one profile listed in theglobalproperty of one of the enabled ImplementationGuides. The Cloud Healthcare API does not currently enforce all of the rules in a StructureDefinition. The following rules are supported: - min/max - minValue/maxValue - maxLength - type - fixed[x] - pattern[x] on simple types - slicing, when using "value" as the discriminator type When a URL cannot be resolved (for example, in a type assertion), the server does not return an error.
Package Details
- Repository
- Google Cloud Native pulumi/pulumi-google-native
- License
- Apache-2.0
Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi