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/v1.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)
// Output-based functions aren't available in Java yet
fn::invoke:
function: google-native:healthcare/v1:getFhirStore
arguments:
# arguments dictionary
The following arguments are supported:
- Dataset
Id string - Fhir
Store stringId - Location string
- Project string
- Dataset
Id string - Fhir
Store stringId - Location string
- Project string
- dataset
Id String - fhir
Store StringId - location String
- project String
- dataset
Id string - fhir
Store stringId - location string
- project string
- dataset_
id str - fhir_
store_ strid - location str
- project str
- dataset
Id String - fhir
Store StringId - location String
- project String
getFhirStore Result
The following output properties are available:
- Complex
Data 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.
- Default
Search boolHandling Strict - If true, overrides the default search behavior for this FHIR store to
handling=strict
which returns an error for unrecognized search parameters. If false, uses the FHIR specification defaulthandling=lenient
which ignores unrecognized search parameters. The handling can always be changed from the default on an individual API call by setting the HTTP headerPrefer: handling=strict
orPrefer: 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 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}
. - Notification
Config Pulumi.Google Native. Healthcare. V1. Outputs. Notification Config Response - Deprecated. Use
notification_configs
instead. 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 List<Pulumi.Google Native. Healthcare. V1. Outputs. Fhir Notification Config Response> - Specifies where and whether to send notifications upon changes to a FHIR store.
- Stream
Configs List<Pulumi.Google Native. Healthcare. V1. 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.dataEditor
role 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 Pulumi.Google Native. Healthcare. V1. 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.
- Complex
Data 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.
- Default
Search boolHandling Strict - If true, overrides the default search behavior for this FHIR store to
handling=strict
which returns an error for unrecognized search parameters. If false, uses the FHIR specification defaulthandling=lenient
which ignores unrecognized search parameters. The handling can always be changed from the default on an individual API call by setting the HTTP headerPrefer: handling=strict
orPrefer: 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 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}
. - Notification
Config NotificationConfig Response - Deprecated. Use
notification_configs
instead. 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 []FhirNotification Config Response - Specifies where and whether to send notifications upon changes to a FHIR store.
- Stream
Configs []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.dataEditor
role 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 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 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.
- default
Search BooleanHandling Strict - If true, overrides the default search behavior for this FHIR store to
handling=strict
which returns an error for unrecognized search parameters. If false, uses the FHIR specification defaulthandling=lenient
which ignores unrecognized search parameters. The handling can always be changed from the default on an individual API call by setting the HTTP headerPrefer: handling=strict
orPrefer: handling=lenient
. - disable
Referential 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.
- disable
Resource 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.
- enable
Update 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}
. - notification
Config NotificationConfig Response - Deprecated. Use
notification_configs
instead. 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 List<FhirNotification Config Response> - Specifies where and whether to send notifications upon changes to a FHIR store.
- stream
Configs 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.dataEditor
role 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 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 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.
- default
Search booleanHandling Strict - If true, overrides the default search behavior for this FHIR store to
handling=strict
which returns an error for unrecognized search parameters. If false, uses the FHIR specification defaulthandling=lenient
which ignores unrecognized search parameters. The handling can always be changed from the default on an individual API call by setting the HTTP headerPrefer: handling=strict
orPrefer: handling=lenient
. - disable
Referential 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.
- disable
Resource 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.
- enable
Update 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}
. - notification
Config NotificationConfig Response - Deprecated. Use
notification_configs
instead. 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 FhirNotification Config Response[] - Specifies where and whether to send notifications upon changes to a FHIR store.
- stream
Configs 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.dataEditor
role 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 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.
- default_
search_ boolhandling_ strict - If true, overrides the default search behavior for this FHIR store to
handling=strict
which returns an error for unrecognized search parameters. If false, uses the FHIR specification defaulthandling=lenient
which ignores unrecognized search parameters. The handling can always be changed from the default on an individual API call by setting the HTTP headerPrefer: handling=strict
orPrefer: 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_configs
instead. 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.
- 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.dataEditor
role 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.
- complex
Data 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.
- default
Search BooleanHandling Strict - If true, overrides the default search behavior for this FHIR store to
handling=strict
which returns an error for unrecognized search parameters. If false, uses the FHIR specification defaulthandling=lenient
which ignores unrecognized search parameters. The handling can always be changed from the default on an individual API call by setting the HTTP headerPrefer: handling=strict
orPrefer: handling=lenient
. - disable
Referential 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.
- disable
Resource 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.
- enable
Update 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}
. - notification
Config Property Map - Deprecated. Use
notification_configs
instead. 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 List<Property Map> - Specifies where and whether to send notifications upon changes to a FHIR store.
- stream
Configs 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.dataEditor
role 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 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
CharacterMaskConfigResponse
- Masking
Character string - Character to mask the sensitive values. If not supplied, defaults to "*".
- Masking
Character string - Character to mask the sensitive values. If not supplied, defaults to "*".
- masking
Character String - Character to mask the sensitive values. If not supplied, defaults to "*".
- masking
Character 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 "*".
- masking
Character String - Character to mask the sensitive values. If not supplied, defaults to "*".
CryptoHashConfigResponse
- Crypto
Key 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
norkms_wrapped
is specified. Must not be set ifkms_wrapped
is set. - Kms
Wrapped Pulumi.Google Native. Healthcare. V1. Inputs. Kms Wrapped Crypto Key Response - KMS wrapped key. Must not be set if
crypto_key
is set.
- Crypto
Key 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
norkms_wrapped
is specified. Must not be set ifkms_wrapped
is set. - Kms
Wrapped KmsWrapped Crypto Key Response - KMS wrapped key. Must not be set if
crypto_key
is set.
- crypto
Key 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
norkms_wrapped
is specified. Must not be set ifkms_wrapped
is set. - kms
Wrapped KmsWrapped Crypto Key Response - KMS wrapped key. Must not be set if
crypto_key
is set.
- crypto
Key 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
norkms_wrapped
is specified. Must not be set ifkms_wrapped
is set. - kms
Wrapped 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
norkms_wrapped
is specified. Must not be set ifkms_wrapped
is set. - kms_
wrapped KmsWrapped Crypto Key Response - KMS wrapped key. Must not be set if
crypto_key
is set.
- crypto
Key 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
norkms_wrapped
is specified. Must not be set ifkms_wrapped
is set. - kms
Wrapped Property Map - KMS wrapped key. Must not be set if
crypto_key
is set.
DateShiftConfigResponse
- Crypto
Key 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, thenkms_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 ifkms_wrapped
is set. - Kms
Wrapped Pulumi.Google Native. Healthcare. V1. Inputs. Kms Wrapped Crypto Key Response - KMS wrapped key. If
kms_wrapped
is not set, thencrypto_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 ifcrypto_key
is set.
- Crypto
Key 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, thenkms_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 ifkms_wrapped
is set. - Kms
Wrapped KmsWrapped Crypto Key Response - KMS wrapped key. If
kms_wrapped
is not set, thencrypto_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 ifcrypto_key
is set.
- crypto
Key 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, thenkms_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 ifkms_wrapped
is set. - kms
Wrapped KmsWrapped Crypto Key Response - KMS wrapped key. If
kms_wrapped
is not set, thencrypto_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 ifcrypto_key
is set.
- crypto
Key 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, thenkms_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 ifkms_wrapped
is set. - kms
Wrapped KmsWrapped Crypto Key Response - KMS wrapped key. If
kms_wrapped
is not set, thencrypto_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 ifcrypto_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, thenkms_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 ifkms_wrapped
is set. - kms_
wrapped KmsWrapped Crypto Key Response - KMS wrapped key. If
kms_wrapped
is not set, thencrypto_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 ifcrypto_key
is set.
- crypto
Key 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, thenkms_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 ifkms_wrapped
is set. - kms
Wrapped Property Map - KMS wrapped key. If
kms_wrapped
is not set, thencrypto_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 ifcrypto_key
is set.
DeidentifiedStoreDestinationResponse
- Config
Pulumi.
Google Native. Healthcare. V1. 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
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
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
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
Deidentify
Config 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
- Dicom
Pulumi.
Google Native. Healthcare. V1. Inputs. Dicom Config Response - Configures de-id of application/DICOM content.
- Fhir
Pulumi.
Google Native. Healthcare. V1. Inputs. Fhir Config Response - Configures de-id of application/FHIR content.
- Image
Pulumi.
Google Native. Healthcare. V1. Inputs. Image Config Response - Configures de-identification of image pixels wherever they are found in the source_dataset.
- Text
Pulumi.
Google Native. Healthcare. V1. Inputs. Text Config 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
LOCATION
orORGANIZATION_NAME
infoTypes.LOCATION
must be excluded within TextConfig, and must also be excluded within ImageConfig if image redaction is required.
- Dicom
Dicom
Config Response - Configures de-id of application/DICOM content.
- Fhir
Fhir
Config Response - Configures de-id of application/FHIR content.
- Image
Image
Config Response - Configures de-identification of image pixels wherever they are found in the source_dataset.
- Text
Text
Config 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
LOCATION
orORGANIZATION_NAME
infoTypes.LOCATION
must be excluded within TextConfig, and must also be excluded within ImageConfig if image redaction is required.
- dicom
Dicom
Config Response - Configures de-id of application/DICOM content.
- fhir
Fhir
Config Response - Configures de-id of application/FHIR content.
- image
Image
Config Response - Configures de-identification of image pixels wherever they are found in the source_dataset.
- text
Text
Config Response - Configures de-identification of text wherever it is found in the source_dataset.
- use
Regional 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
LOCATION
orORGANIZATION_NAME
infoTypes.LOCATION
must be excluded within TextConfig, and must also be excluded within ImageConfig if image redaction is required.
- dicom
Dicom
Config Response - Configures de-id of application/DICOM content.
- fhir
Fhir
Config Response - Configures de-id of application/FHIR content.
- image
Image
Config Response - Configures de-identification of image pixels wherever they are found in the source_dataset.
- text
Text
Config Response - Configures de-identification of text wherever it is found in the source_dataset.
- use
Regional 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
LOCATION
orORGANIZATION_NAME
infoTypes.LOCATION
must be excluded within TextConfig, and must also be excluded within ImageConfig if image redaction is required.
- dicom
Dicom
Config Response - Configures de-id of application/DICOM content.
- fhir
Fhir
Config Response - Configures de-id of application/FHIR content.
- image
Image
Config Response - Configures de-identification of image pixels wherever they are found in the source_dataset.
- text
Text
Config 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
LOCATION
orORGANIZATION_NAME
infoTypes.LOCATION
must be excluded within TextConfig, and must also be excluded within ImageConfig if image redaction is required.
- dicom Property Map
- Configures de-id of application/DICOM content.
- fhir Property Map
- Configures de-id of application/FHIR content.
- image Property Map
- Configures de-identification of image pixels wherever they are found in the source_dataset.
- text Property Map
- Configures de-identification of text wherever it is found in the source_dataset.
- use
Regional 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
LOCATION
orORGANIZATION_NAME
infoTypes.LOCATION
must be excluded within TextConfig, and must also be excluded within ImageConfig if image redaction is required.
DicomConfigResponse
- Filter
Profile string - Tag filtering profile that determines which tags to keep/remove.
- Keep
List Pulumi.Google Native. Healthcare. V1. Inputs. Tag Filter List Response - List of tags to keep. Remove all other tags.
- Remove
List Pulumi.Google Native. Healthcare. V1. Inputs. Tag Filter 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
- Filter
Profile string - 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
- filter
Profile String - 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 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 string - 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 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
- filter
Profile String - Tag filtering profile that determines which tags to keep/remove.
- keep
List Property Map - List of tags to keep. Remove all other tags.
- remove
List Property Map - List of tags to remove. Keep all other tags.
- skip
Id 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
FhirConfigResponse
- 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 List<Pulumi.List Google Native. Healthcare. V1. 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
.
- 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 []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
.
- default
Keep 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.
- field
Metadata 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
.
- default
Keep 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.
- field
Metadata 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
.
- 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
.
- default
Keep 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.
- field
Metadata 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
.
FhirNotificationConfigResponse
- Pubsub
Topic string - The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a
PubsubMessage
with the following fields: *PubsubMessage.Data
contains the resource name. *PubsubMessage.MessageId
is the ID of this notification. It is guaranteed to be unique within the topic. *PubsubMessage.PublishTime
is 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.
- 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.
- Pubsub
Topic string - The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a
PubsubMessage
with the following fields: *PubsubMessage.Data
contains the resource name. *PubsubMessage.MessageId
is the ID of this notification. It is guaranteed to be unique within the topic. *PubsubMessage.PublishTime
is 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.
- 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.
- pubsub
Topic String - The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a
PubsubMessage
with the following fields: *PubsubMessage.Data
contains the resource name. *PubsubMessage.MessageId
is the ID of this notification. It is guaranteed to be unique within the topic. *PubsubMessage.PublishTime
is 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 BooleanResource - Whether to send full FHIR resource to this Pub/Sub topic.
- send
Previous 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 string - The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a
PubsubMessage
with the following fields: *PubsubMessage.Data
contains the resource name. *PubsubMessage.MessageId
is the ID of this notification. It is guaranteed to be unique within the topic. *PubsubMessage.PublishTime
is 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 booleanResource - Whether to send full FHIR resource to this Pub/Sub topic.
- send
Previous 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
PubsubMessage
with the following fields: *PubsubMessage.Data
contains the resource name. *PubsubMessage.MessageId
is the ID of this notification. It is guaranteed to be unique within the topic. *PubsubMessage.PublishTime
is 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.
- 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.
- pubsub
Topic String - The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a
PubsubMessage
with the following fields: *PubsubMessage.Data
contains the resource name. *PubsubMessage.MessageId
is the ID of this notification. It is guaranteed to be unique within the topic. *PubsubMessage.PublishTime
is 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 BooleanResource - Whether to send full FHIR resource to this Pub/Sub topic.
- send
Previous 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.
FieldMetadataResponse
- Action string
- Deidentify action for one field.
- Paths List<string>
- List of paths to FHIR fields to be redacted. Each path is a period-separated list where each component is either a field name or FHIR type name, for example: Patient, HumanName. For "choice" types (those defined in the FHIR spec with the form: field[x]) we 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.
- Action string
- Deidentify action for one field.
- Paths []string
- List of paths to FHIR fields to be redacted. Each path is a period-separated list where each component is either a field name or FHIR type name, for example: Patient, HumanName. For "choice" types (those defined in the FHIR spec with the form: field[x]) we 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.
- action String
- Deidentify action for one field.
- paths List<String>
- List of paths to FHIR fields to be redacted. Each path is a period-separated list where each component is either a field name or FHIR type name, for example: Patient, HumanName. For "choice" types (those defined in the FHIR spec with the form: field[x]) we 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.
- action string
- Deidentify action for one field.
- paths string[]
- List of paths to FHIR fields to be redacted. Each path is a period-separated list where each component is either a field name or FHIR type name, for example: Patient, HumanName. For "choice" types (those defined in the FHIR spec with the form: field[x]) we 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.
- action str
- Deidentify action for one field.
- paths Sequence[str]
- List of paths to FHIR fields to be redacted. Each path is a period-separated list where each component is either a field name or FHIR type name, for example: Patient, HumanName. For "choice" types (those defined in the FHIR spec with the form: field[x]) we 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.
- action String
- Deidentify action for one field.
- paths List<String>
- List of paths to FHIR fields to be redacted. Each path is a period-separated list where each component is either a field name or FHIR type name, for example: Patient, HumanName. For "choice" types (those defined in the FHIR spec with the form: field[x]) we 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.
GoogleCloudHealthcareV1FhirBigQueryDestinationResponse
- Dataset
Uri string - BigQuery URI to an existing dataset, up to 2000 characters long, in the format
bq://projectId.bqDatasetId
. - Force bool
- If this flag is
TRUE
, all tables are deleted from the dataset before the new exported tables are written. If the flag is not set and the destination dataset contains tables, the export call returns an error. Ifwrite_disposition
is 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 Pulumi.Google Native. Healthcare. V1. Inputs. Schema Config Response - The configuration for the exported BigQuery schema.
- Write
Disposition 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
force
parameter is ignored.
- Dataset
Uri string - BigQuery URI to an existing dataset, up to 2000 characters long, in the format
bq://projectId.bqDatasetId
. - Force bool
- If this flag is
TRUE
, all tables are deleted from the dataset before the new exported tables are written. If the flag is not set and the destination dataset contains tables, the export call returns an error. Ifwrite_disposition
is 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 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
force
parameter is ignored.
- dataset
Uri String - BigQuery URI to an existing dataset, up to 2000 characters long, in the format
bq://projectId.bqDatasetId
. - force Boolean
- If this flag is
TRUE
, all tables are deleted from the dataset before the new exported tables are written. If the flag is not set and the destination dataset contains tables, the export call returns an error. Ifwrite_disposition
is 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 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
force
parameter is ignored.
- dataset
Uri string - BigQuery URI to an existing dataset, up to 2000 characters long, in the format
bq://projectId.bqDatasetId
. - force boolean
- If this flag is
TRUE
, all tables are deleted from the dataset before the new exported tables are written. If the flag is not set and the destination dataset contains tables, the export call returns an error. Ifwrite_disposition
is 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 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
force
parameter is ignored.
- dataset_
uri str - BigQuery URI to an existing dataset, up to 2000 characters long, in the format
bq://projectId.bqDatasetId
. - force bool
- If this flag is
TRUE
, all tables are deleted from the dataset before the new exported tables are written. If the flag is not set and the destination dataset contains tables, the export call returns an error. Ifwrite_disposition
is 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
force
parameter is ignored.
- dataset
Uri String - BigQuery URI to an existing dataset, up to 2000 characters long, in the format
bq://projectId.bqDatasetId
. - force Boolean
- If this flag is
TRUE
, all tables are deleted from the dataset before the new exported tables are written. If the flag is not set and the destination dataset contains tables, the export call returns an error. Ifwrite_disposition
is 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 Property Map - The configuration for the exported BigQuery schema.
- write
Disposition 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
force
parameter is ignored.
ImageConfigResponse
- Text
Redaction stringMode - Determines how to redact text from image.
- Text
Redaction stringMode - Determines how to redact text from image.
- text
Redaction StringMode - Determines how to redact text from image.
- text
Redaction stringMode - Determines how to redact text from image.
- text_
redaction_ strmode - Determines how to redact text from image.
- text
Redaction StringMode - Determines how to redact text from image.
InfoTypeTransformationResponse
- Character
Mask Pulumi.Config Google Native. Healthcare. V1. Inputs. Character Mask Config Response - Config for character mask.
- Crypto
Hash Pulumi.Config Google Native. Healthcare. V1. Inputs. Crypto Hash Config Response - Config for crypto hash.
- Date
Shift Pulumi.Config Google Native. Healthcare. V1. Inputs. Date Shift Config Response - Config for date shift.
- Info
Types List<string> - InfoTypes to apply this transformation to. If this is not specified, the transformation applies to any info_type.
- Redact
Config Pulumi.Google Native. Healthcare. V1. Inputs. Redact Config Response - Config for text redaction.
- Replace
With Pulumi.Info Type Config Google Native. Healthcare. V1. Inputs. Replace 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 []string - InfoTypes to apply this transformation to. If this is not specified, the transformation applies to any info_type.
- Redact
Config RedactConfig Response - Config for text redaction.
- Replace
With 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 List<String> - InfoTypes to apply this transformation to. If this is not specified, the transformation applies to any info_type.
- redact
Config RedactConfig Response - Config for text redaction.
- replace
With 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 string[] - InfoTypes to apply this transformation to. If this is not specified, the transformation applies to any info_type.
- redact
Config RedactConfig Response - Config for text redaction.
- replace
With 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] - InfoTypes to apply this transformation to. If this is not specified, the transformation applies to any info_type.
- redact_
config RedactConfig Response - Config for text redaction.
- replace_
with_ Replaceinfo_ type_ config With Info Type Config Response - Config for replace with InfoType.
- character
Mask Property MapConfig - Config for character mask.
- crypto
Hash Property MapConfig - Config for crypto hash.
- date
Shift Property MapConfig - Config for date shift.
- info
Types List<String> - InfoTypes to apply this transformation to. If this is not specified, the transformation applies to any info_type.
- redact
Config Property Map - Config for text redaction.
- replace
With Property MapInfo Type Config - Config for replace with InfoType.
KmsWrappedCryptoKeyResponse
- Crypto
Key string - 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 string - The wrapped data crypto key.
- Crypto
Key string - 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 string - The wrapped data crypto key.
- crypto
Key String - 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 String - The wrapped data crypto key.
- crypto
Key string - 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 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.
- crypto
Key String - 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 String - The wrapped data crypto key.
NotificationConfigResponse
- Pubsub
Topic 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.
- Send
For boolBulk Import - Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
- Pubsub
Topic 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.
- Send
For boolBulk Import - Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
- pubsub
Topic 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.
- send
For BooleanBulk Import - Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
- pubsub
Topic 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.
- send
For 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.
- pubsub
Topic 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.
- send
For BooleanBulk Import - Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
SchemaConfigResponse
- Last
Updated Pulumi.Partition Config Google Native. Healthcare. V1. Inputs. Time Partitioning Response - The configuration for exported BigQuery tables to be partitioned by FHIR resource's last updated time column.
- Recursive
Structure stringDepth - The depth for all recursive structures in the output analytics schema. For example,
concept
in the CodeSystem resource is a recursive structure; when the depth is 2, the CodeSystem table will have a column calledconcept.concept
but 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 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 stringDepth - The depth for all recursive structures in the output analytics schema. For example,
concept
in the CodeSystem resource is a recursive structure; when the depth is 2, the CodeSystem table will have a column calledconcept.concept
but 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 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 StringDepth - The depth for all recursive structures in the output analytics schema. For example,
concept
in the CodeSystem resource is a recursive structure; when the depth is 2, the CodeSystem table will have a column calledconcept.concept
but 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 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 stringDepth - The depth for all recursive structures in the output analytics schema. For example,
concept
in the CodeSystem resource is a recursive structure; when the depth is 2, the CodeSystem table will have a column calledconcept.concept
but 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 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,
concept
in the CodeSystem resource is a recursive structure; when the depth is 2, the CodeSystem table will have a column calledconcept.concept
but 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.
- last
Updated Property MapPartition Config - The configuration for exported BigQuery tables to be partitioned by FHIR resource's last updated time column.
- recursive
Structure StringDepth - The depth for all recursive structures in the output analytics schema. For example,
concept
in the CodeSystem resource is a recursive structure; when the depth is 2, the CodeSystem table will have a column calledconcept.concept
but 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 String - Specifies the output schema type. Schema type is required.
StreamConfigResponse
- Bigquery
Destination Pulumi.Google Native. Healthcare. V1. Inputs. Google Cloud Healthcare V1Fhir 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. For example, "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. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any resource mutation that generates more than 1 MB of BigQuery data is not streamed. 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. 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 are logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging).
- Deidentified
Store Pulumi.Destination Google Native. Healthcare. V1. 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).
- Resource
Types 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.
- Bigquery
Destination GoogleCloud Healthcare V1Fhir 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. For example, "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. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any resource mutation that generates more than 1 MB of BigQuery data is not streamed. 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. 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 are logged to Cloud Logging. For more information, 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 []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 V1Fhir 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. For example, "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. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any resource mutation that generates more than 1 MB of BigQuery data is not streamed. 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. 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 are logged to Cloud Logging. For more information, 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 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.
- bigquery
Destination GoogleCloud Healthcare V1Fhir 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. For example, "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. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any resource mutation that generates more than 1 MB of BigQuery data is not streamed. 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. 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 are logged to Cloud Logging. For more information, 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 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 V1Fhir 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. For example, "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. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any resource mutation that generates more than 1 MB of BigQuery data is not streamed. 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. 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 are logged to Cloud Logging. For more information, 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.
- bigquery
Destination 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. For example, "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. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any resource mutation that generates more than 1 MB of BigQuery data is not streamed. 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. 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 are logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging).
- deidentified
Store 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).
- resource
Types 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
- Additional
Transformations List<Pulumi.Google Native. Healthcare. V1. Inputs. Info Type Transformation Response> - Transformations to apply to the detected data, overridden by
exclude_info_types
. - Exclude
Info List<string>Types - InfoTypes to skip transforming, overriding
additional_transformations
. - Transformations
List<Pulumi.
Google Native. Healthcare. V1. Inputs. Info Type Transformation Response> - The transformations to apply to the detected data. Deprecated. Use
additional_transformations
instead.
- Additional
Transformations []InfoType Transformation Response - Transformations to apply to the detected data, overridden by
exclude_info_types
. - Exclude
Info []stringTypes - InfoTypes to skip transforming, overriding
additional_transformations
. - Transformations
[]Info
Type Transformation Response - The transformations to apply to the detected data. Deprecated. Use
additional_transformations
instead.
- additional
Transformations List<InfoType Transformation Response> - Transformations to apply to the detected data, overridden by
exclude_info_types
. - exclude
Info List<String>Types - InfoTypes to skip transforming, overriding
additional_transformations
. - transformations
List<Info
Type Transformation Response> - The transformations to apply to the detected data. Deprecated. Use
additional_transformations
instead.
- additional
Transformations InfoType Transformation Response[] - Transformations to apply to the detected data, overridden by
exclude_info_types
. - exclude
Info string[]Types - InfoTypes to skip transforming, overriding
additional_transformations
. - transformations
Info
Type Transformation Response[] - The transformations to apply to the detected data. Deprecated. Use
additional_transformations
instead.
- additional_
transformations Sequence[InfoType Transformation Response] - Transformations to apply to the detected data, overridden by
exclude_info_types
. - exclude_
info_ Sequence[str]types - InfoTypes to skip transforming, overriding
additional_transformations
. - transformations
Sequence[Info
Type Transformation Response] - The transformations to apply to the detected data. Deprecated. Use
additional_transformations
instead.
- additional
Transformations List<Property Map> - Transformations to apply to the detected data, overridden by
exclude_info_types
. - exclude
Info List<String>Types - InfoTypes to skip transforming, overriding
additional_transformations
. - transformations List<Property Map>
- The transformations to apply to the detected data. Deprecated. Use
additional_transformations
instead.
TimePartitioningResponse
- Expiration
Ms string - Number of milliseconds for which to keep the storage for a partition.
- Type string
- Type of partitioning.
- Expiration
Ms string - Number of milliseconds for which to keep the storage for a partition.
- Type string
- Type of partitioning.
- expiration
Ms String - Number of milliseconds for which to keep the storage for a partition.
- type String
- Type of partitioning.
- expiration
Ms 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.
- expiration
Ms String - Number of milliseconds for which to keep the storage for a partition.
- type String
- Type of partitioning.
ValidationConfigResponse
- 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 structure definitions 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 List<string>Guides - A list of implementation guide 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_guides
to["http://hl7.org/fhir/us/core/ImplementationGuide/ig"]
. Ifenabled_implementation_guides
is 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 theglobal
property 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 structure definitions 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 []stringGuides - A list of implementation guide 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_guides
to["http://hl7.org/fhir/us/core/ImplementationGuide/ig"]
. Ifenabled_implementation_guides
is 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 theglobal
property 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 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.
- disable
Profile BooleanValidation - Whether to disable profile validation for this FHIR store. Set this to true to disable checking incoming resources for conformance against structure definitions in this FHIR store.
- disable
Reference 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.
- disable
Required 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.
- enabled
Implementation List<String>Guides - A list of implementation guide 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_guides
to["http://hl7.org/fhir/us/core/ImplementationGuide/ig"]
. Ifenabled_implementation_guides
is 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 theglobal
property 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 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.
- disable
Profile booleanValidation - Whether to disable profile validation for this FHIR store. Set this to true to disable checking incoming resources for conformance against structure definitions in this FHIR store.
- disable
Reference 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.
- disable
Required 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.
- enabled
Implementation string[]Guides - A list of implementation guide 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_guides
to["http://hl7.org/fhir/us/core/ImplementationGuide/ig"]
. Ifenabled_implementation_guides
is 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 theglobal
property 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 structure definitions 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 implementation guide 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_guides
to["http://hl7.org/fhir/us/core/ImplementationGuide/ig"]
. Ifenabled_implementation_guides
is 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 theglobal
property 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 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.
- disable
Profile BooleanValidation - Whether to disable profile validation for this FHIR store. Set this to true to disable checking incoming resources for conformance against structure definitions in this FHIR store.
- disable
Reference 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.
- disable
Required 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.
- enabled
Implementation List<String>Guides - A list of implementation guide 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_guides
to["http://hl7.org/fhir/us/core/ImplementationGuide/ig"]
. Ifenabled_implementation_guides
is 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 theglobal
property 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