feat(healthcare): update the api

#### healthcare:v1beta1

The following keys were deleted:
- resources.projects.resources.locations.resources.datasets.resources.annotationStores.methods.create (Total Keys: 14)
- resources.projects.resources.locations.resources.datasets.resources.annotationStores.methods.delete (Total Keys: 11)
- resources.projects.resources.locations.resources.datasets.resources.annotationStores.methods.evaluate (Total Keys: 12)
- resources.projects.resources.locations.resources.datasets.resources.annotationStores.methods.export (Total Keys: 12)
- resources.projects.resources.locations.resources.datasets.resources.annotationStores.methods.get (Total Keys: 11)
- resources.projects.resources.locations.resources.datasets.resources.annotationStores.methods.import (Total Keys: 12)
- resources.projects.resources.locations.resources.datasets.resources.annotationStores.methods.list (Total Keys: 18)
- resources.projects.resources.locations.resources.datasets.resources.annotationStores.methods.patch (Total Keys: 15)
- resources.projects.resources.locations.resources.datasets.resources.annotationStores.resources.annotations.methods.create (Total Keys: 12)
- resources.projects.resources.locations.resources.datasets.resources.annotationStores.resources.annotations.methods.delete (Total Keys: 11)
- resources.projects.resources.locations.resources.datasets.resources.annotationStores.resources.annotations.methods.get (Total Keys: 11)
- resources.projects.resources.locations.resources.datasets.resources.annotationStores.resources.annotations.methods.list (Total Keys: 20)
- resources.projects.resources.locations.resources.datasets.resources.annotationStores.resources.annotations.methods.patch (Total Keys: 15)
- schemas.Annotation (Total Keys: 21)
- schemas.BoundingPoly (Total Keys: 5)
- schemas.CloudHealthcareSource (Total Keys: 3)
- schemas.DeidentifyConfig.properties.annotation.$ref (Total Keys: 1)
- schemas.Detail (Total Keys: 4)
- schemas.EvaluateAnnotationStoreRequest (Total Keys: 9)
- schemas.EvaluateAnnotationStoreResponse (Total Keys: 2)
- schemas.ExportAnnotationsRequest (Total Keys: 4)
- schemas.ExportAnnotationsResponse (Total Keys: 2)
- schemas.FilterList (Total Keys: 4)
- schemas.Finding (Total Keys: 8)
- schemas.GoogleCloudHealthcareV1beta1AnnotationBigQueryDestination (Total Keys: 6)
- schemas.GoogleCloudHealthcareV1beta1AnnotationGcsDestination (Total Keys: 3)
- schemas.GoogleCloudHealthcareV1beta1AnnotationGcsSource (Total Keys: 3)
- schemas.ImageAnnotation (Total Keys: 6)
- schemas.ImportAnnotationsRequest (Total Keys: 3)
- schemas.ImportAnnotationsResponse (Total Keys: 2)
- schemas.InfoTypeConfig (Total Keys: 5)
- schemas.ListAnnotationStoresResponse (Total Keys: 5)
- schemas.ListAnnotationsResponse (Total Keys: 5)
- schemas.ResourceAnnotation (Total Keys: 3)
- schemas.SensitiveTextAnnotation (Total Keys: 4)
- schemas.Vertex (Total Keys: 6)

Author: yoshi-automation

docs/dyn/healthcare_v1.projects.locations.datasets.fhirStores.fhir.html

@@ -197,7 +197,7 @@ <h3>Method Details</h3>
   <pre>Creates a new dataset containing de-identified data from the source dataset. The metadata field type is OperationMetadata. If the request is successful, the response field type is DeidentifySummary. If errors occur, error is set. The LRO result may still be successful if de-identification fails for some DICOM instances. The new de-identified dataset will not contain these failed resources. Failed resource totals are tracked in Operation.metadata. Error details are also logged to Cloud Logging. For more information, see [Viewing error logs in Cloud Logging](https://cloud.google.com/healthcare/docs/how-tos/logging).
 
 Args:
-  sourceDataset: string, Required. Source dataset resource name. For example, `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}`. (required)
+  sourceDataset: string, Required. Source dataset resource name. For example, `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}`. R5 FHIR stores are not supported and will be skipped. (required)
   body: object, The request body.
     The object takes the form of:
 

docs/dyn/healthcare_v1.projects.locations.datasets.fhirStores.html

@@ -221,10 +221,6 @@ <h3>Method Details</h3>
 
 { # Creates a new DICOM store with sensitive information de-identified.
   &quot;config&quot;: { # Configures de-id options specific to different types of content. Each submessage customizes the handling of an https://tools.ietf.org/html/rfc6838 media type or subtype. Configs are applied in a nested manner at runtime. # Deidentify configuration. Only one of `config` and `gcs_config_uri` can be specified.
-    &quot;annotation&quot;: { # Specifies how to store annotations during de-identification operation. # Configures how annotations, meaning that the location and infoType of sensitive information findings, are created during de-identification. If unspecified, no annotations are created.
-      &quot;annotationStoreName&quot;: &quot;A String&quot;, # The name of the annotation store, in the form `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/annotationStores/{annotation_store_id}`). * The destination annotation store must be in the same project as the source data. De-identifying data across multiple projects is not supported. * The destination annotation store must exist when using DeidentifyDicomStore or DeidentifyFhirStore. DeidentifyDataset automatically creates the destination annotation store.
-      &quot;storeQuote&quot;: True or False, # If set to true, the sensitive texts are included in SensitiveTextAnnotation of Annotation.
-    },
     &quot;dicom&quot;: { # Specifies the parameters needed for de-identification of DICOM stores. # Configures de-id of application/DICOM content. Deprecated. Use `dicom_tag_config` instead.
       &quot;filterProfile&quot;: &quot;A String&quot;, # Tag filtering profile that determines which tags to keep/remove.
       &quot;keepList&quot;: { # List of tags to be filtered. # List of tags to keep. Remove all other tags.

docs/dyn/healthcare_v1.projects.locations.datasets.html

@@ -202,16 +202,12 @@ <h3>Method Details</h3>
   <pre>Creates a new dataset containing de-identified data from the source dataset. The metadata field type is OperationMetadata. If the request is successful, the response field type is DeidentifySummary. The LRO result may still be successful if de-identification fails for some resources. The new de-identified dataset will not contain these failed resources. The number of resources processed are tracked in Operation.metadata. Error details are logged to Cloud Logging. For more information, see [Viewing error logs in Cloud Logging](https://cloud.google.com/healthcare/docs/how-tos/logging).
 
 Args:
-  sourceDataset: string, Required. Source dataset resource name. For example, `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}`. (required)
+  sourceDataset: string, Required. Source dataset resource name. For example, `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}`. R5 FHIR stores are not supported and will be skipped. (required)
   body: object, The request body.
     The object takes the form of:
 
 { # Redacts identifying information from the specified dataset.
   &quot;config&quot;: { # Configures de-id options specific to different types of content. Each submessage customizes the handling of an https://tools.ietf.org/html/rfc6838 media type or subtype. Configs are applied in a nested manner at runtime. # Deidentify configuration. Only one of `config` and `gcs_config_uri` can be specified.
-    &quot;annotation&quot;: { # Specifies how to store annotations during de-identification operation. # Configures how annotations, meaning that the location and infoType of sensitive information findings, are created during de-identification. If unspecified, no annotations are created.
-      &quot;annotationStoreName&quot;: &quot;A String&quot;, # The name of the annotation store, in the form `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/annotationStores/{annotation_store_id}`). * The destination annotation store must be in the same project as the source data. De-identifying data across multiple projects is not supported. * The destination annotation store must exist when using DeidentifyDicomStore or DeidentifyFhirStore. DeidentifyDataset automatically creates the destination annotation store.
-      &quot;storeQuote&quot;: True or False, # If set to true, the sensitive texts are included in SensitiveTextAnnotation of Annotation.
-    },
     &quot;dicom&quot;: { # Specifies the parameters needed for de-identification of DICOM stores. # Configures de-id of application/DICOM content. Deprecated. Use `dicom_tag_config` instead.
       &quot;filterProfile&quot;: &quot;A String&quot;, # Tag filtering profile that determines which tags to keep/remove.
       &quot;keepList&quot;: { # List of tags to be filtered. # List of tags to keep. Remove all other tags.