Transitioning to the v1beta1 API

This page explains the key differences between v1alpha2 and v1beta1 of the Cloud Healthcare API. It also provides examples of how to transition from v1alpha2 to v1beta1.

REST paths

All REST paths to the Cloud Healthcare API now use v1beta1 instead of v1alpha2. For example:

v1alpha2:

GET https://healthcare.googleapis.com/v1alpha2/projects/PROJECT_ID/locations/REGION/datasets/DATASET_ID

v1beta1:

GET https://healthcare.googleapis.com/v1beta1/projects/PROJECT_ID/locations/REGION/datasets/DATASET_ID

FHIR changes

FHIR store capability statement

The fhirStores.capabilities method is no longer available. Instead, use fhirStores.fhir.capabilities.

For example:

v1alpha2:

GET https://healthcare.googleapis.com/v1alpha2/projects/PROJECT_ID/locations/REGION/datasets/DATASET_ID/fhirStores/FHIR_STORE_ID/metadata

v1beta1:

GET https://healthcare.googleapis.com/v1beta1/projects/PROJECT_ID/locations/REGION/datasets/DATASET_ID/fhirStores/FHIR_STORE_ID/fhir/metadata

Error logging during FHIR import

It is no longer possible to write errors to a Cloud Storage object when importing FHIR resources. Instead, view errors in Stackdriver Logging .

IAM permissions for FHIR security labels

It is no longer possible to get and set IAM permissions on FHIR security labels.

Hat Ihnen diese Seite weitergeholfen? Teilen Sie uns Ihr Feedback mit:

Feedback geben zu...

Cloud Healthcare API