Google Cloud Healthcare
Manage, store, and access healthcare data in Google Cloud Platform (Google OAuth2).
OCNORA ships 11 typed Google Cloud Healthcare operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google Cloud Healthcare
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google Cloud Healthcare
Operations, grouped by what they do to your data.
Create and send 2
Read and search 4
Update 2
Delete and cancel 2
Other operations 1
A sample Google Cloud Healthcare workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud Healthcare trigger is needed.
- 2Get Datasetcloud_healthcare.get_datasetGets any metadata associated with a dataset.
- 3Create Datasetcloud_healthcare.create_datasetCreates a new health dataset.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 11
- Create DatasetCreates a new health dataset.cloud_healthcare.create_dataset
- Create Fhir StoreCreates a new FHIR store within the parent dataset.cloud_healthcare.create_fhir_store
- Deidentify DatasetCreates a new dataset containing de-identified data from the source dataset. The metadata field type is OperationMetadata.cloud_healthcare.deidentify_dataset
- Delete DatasetDeletes the specified health dataset and all data contained in the dataset.cloud_healthcare.delete_dataset
- Delete Fhir StoreDeletes the specified FHIR store and removes all resources within it.cloud_healthcare.delete_fhir_store
- Get DatasetGets any metadata associated with a dataset.cloud_healthcare.get_dataset
- Get Fhir StoreGets the configuration of the specified FHIR store.cloud_healthcare.get_fhir_store
- List DatasetsLists the health datasets in the current project.cloud_healthcare.list_datasets
- List Fhir StoresLists the FHIR stores in the given dataset.cloud_healthcare.list_fhir_stores
- Update DatasetUpdates dataset metadata.cloud_healthcare.update_dataset
- Update Fhir StoreUpdates the configuration of the specified FHIR store.cloud_healthcare.update_fhir_store
Google Cloud Healthcare questions
- How does OCNORA authenticate with Google Cloud Healthcare?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google Cloud Healthcare?
- 11 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Cloud Healthcare operation I need is not listed?
- Where Google Cloud Healthcare has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google Cloud Healthcare?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Cloud Healthcare calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google Cloud Healthcare workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.