Googleapis Healthcare

Connector for the googleapis-healthcare API, generated deterministically from its OpenAPI spec (endpoints, auth, and methods match the spec exactly — nothing is invented).

• Base URL: https://healthcare.googleapis.com
• Auth: OAuth 2.0 (user-delegated) — attach an InTouch oauth credential. Mint one with itcli.py /oauth <provider> (device-code) or /google-auth (Google); the server auto-refreshes the access token before each run, so the connector never handles or stores tokens.

Operations

• healthcare_projects_locations_datasets_operation — GET /v1beta1/{name} — Gets the latest state of a long-running operation. Clients can use this method t
• healthcare_projects_locations_datasets_fhirstore — GET /v1beta1/{name}/$everything — Retrieves a Patient resource and resources related to that patient. Implements t
• healthcare_projects_locations_list — GET /v1beta1/{name}/locations — Lists information about the supported locations for this service.
• healthcare_projects_locations_datasets_consentst — GET /v1beta1/{name}:listRevisions — Lists the revisions of the specified Consent in reverse chronological order.
• healthcare_projects_locations_datasets_annotatio — GET /v1beta1/{parent}/annotationStores — Lists the Annotation stores in the given dataset for a source store.
• healthcare_projects_locations_datasets_list — GET /v1beta1/{parent}/datasets — Lists the health datasets in the current project.

Inputs

• a linked oauth credential (no key inputs) — the server injects a fresh Authorization: Bearer from it
• operation — one of the operations above
• path parameters when an operation's path contains {...}
• query — optional JSON object of query params
• body — JSON object for create/update ops

Example

operation: healthcare_projects_locations_datasets_operation
# (attach an 'oauth' credential to the task — no inline secrets)