Google Cloud Healthcare
Google Cloud Healthcare API is a fully managed, HIPAA-eligible service for ingesting, storing, analyzing, and integrating healthcare data in the cloud. It provides native support for FHIR R4 (Fast Healthcare Interoperability Resources), HL7v2 clinical event messaging, and DICOM medical imaging standards, along with automated de-identification of protected health information (PHI). The API enables healthcare organizations to build interoperable data pipelines, connect clinical systems, and power machine learning applications on Google Cloud infrastructure.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Google Cloud Healthcare the way a machine reads it — 168 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Google Cloud Healthcare scores 61.7/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Google Cloud Healthcare
Each block below is one kind of artifact we hold for Google Cloud Healthcare. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Cloud Healthcare FHIR API
The Cloud Healthcare FHIR API provides a fully managed implementation of the HL7 FHIR standard (supporting DSTU2, STU3, and R4 versions) for storing and querying clinical and ad...
Cloud Healthcare HL7v2 API
The Cloud Healthcare HL7v2 API provides managed ingestion, storage, and retrieval of HL7 version 2.x messages, which are the most widely used standard for exchanging clinical da...
Cloud Healthcare DICOM API
The Cloud Healthcare DICOM API implements the DICOMweb standard for storing, querying, and retrieving medical imaging data including X-rays, CT scans, MRIs, and ultrasounds. It ...
Cloud Healthcare De-identification API
The Cloud Healthcare De-identification API provides automated redaction and transformation of protected health information (PHI) and personally identifiable information (PII) in...
Cloud Healthcare Consent Management API
The Cloud Healthcare Consent Management API provides fine-grained, patient-centric consent management for healthcare data access. It enables organizations to define consent poli...
Google Cloud Healthcare projects API
The projects API from Google Cloud Healthcare — 111 operation(s) for projects.
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Google Cloud Healthcare Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Spectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Google Cloud Healthcare API Rules
SPECTRALJSON Schema 147
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ActivateConsentRequest
JSON SCHEMAAnalyzeEntitiesRequest
JSON SCHEMAAnalyzeEntitiesResponse
JSON SCHEMAArchiveUserDataMappingRequest
JSON SCHEMAArchiveUserDataMappingResponse
JSON SCHEMAAttribute
JSON SCHEMAAttributeDefinition
JSON SCHEMAAuditConfig
JSON SCHEMAAuditLogConfig
JSON SCHEMABinding
JSON SCHEMACancelOperationRequest
JSON SCHEMACharacterMaskConfig
JSON SCHEMACheckDataAccessRequest
JSON SCHEMACheckDataAccessResponse
JSON SCHEMAConsent
JSON SCHEMAConsentArtifact
JSON SCHEMAConsentEvaluation
JSON SCHEMAConsentList
JSON SCHEMAConsentStore
JSON SCHEMACreateMessageRequest
JSON SCHEMACryptoHashConfig
JSON SCHEMADataset
JSON SCHEMADateShiftConfig
JSON SCHEMADeidentifiedStoreDestination
JSON SCHEMADeidentifyConfig
JSON SCHEMADeidentifyDatasetRequest
JSON SCHEMADeidentifyDicomStoreRequest
JSON SCHEMADeidentifyFhirStoreRequest
JSON SCHEMADeidentifySummary
JSON SCHEMADicomConfig
JSON SCHEMADicomFilterConfig
JSON SCHEMADicomStore
JSON SCHEMADicomStoreMetrics
JSON SCHEMAEmpty
JSON SCHEMAEntity
JSON SCHEMAEntityMention
JSON SCHEMAEntityMentionRelationship
JSON SCHEMAEvaluateUserConsentsRequest
JSON SCHEMAEvaluateUserConsentsResponse
JSON SCHEMAExportDicomDataRequest
JSON SCHEMAExportDicomDataResponse
JSON SCHEMAExportMessagesRequest
JSON SCHEMAExportMessagesResponse
JSON SCHEMAExportResourcesRequest
JSON SCHEMAExportResourcesResponse
JSON SCHEMAExpr
JSON SCHEMAFeature
JSON SCHEMAFhirConfig
JSON SCHEMAFhirFilter
JSON SCHEMAFhirNotificationConfig
JSON SCHEMAFhirStore
JSON SCHEMAFhirStoreMetric
JSON SCHEMAFhirStoreMetrics
JSON SCHEMAField
JSON SCHEMAFieldMetadata
JSON SCHEMAGcsDestination
JSON SCHEMAGcsSource
JSON SCHEMAGoogleCloudHealthcareV1ConsentGcsDestination
JSON SCHEMAGoogleCloudHealthcareV1ConsentPolicy
JSON SCHEMAGoogleCloudHealthcareV1DicomGcsDestination
JSON SCHEMAGoogleCloudHealthcareV1DicomGcsSource
JSON SCHEMAGoogleCloudHealthcareV1DicomStreamConfig
JSON SCHEMAGoogleCloudHealthcareV1FhirGcsDestination
JSON SCHEMAGoogleCloudHealthcareV1FhirGcsSource
JSON SCHEMAGroupOrSegment
JSON SCHEMAHl7SchemaConfig
JSON SCHEMAHl7TypesConfig
JSON SCHEMAHl7V2NotificationConfig
JSON SCHEMAHl7V2Store
JSON SCHEMAHl7V2StoreMetric
JSON SCHEMAHl7V2StoreMetrics
JSON SCHEMAHttpBody
JSON SCHEMAImage
JSON SCHEMAImageConfig
JSON SCHEMAImportDicomDataRequest
JSON SCHEMAImportDicomDataResponse
JSON SCHEMAImportMessagesRequest
JSON SCHEMAImportMessagesResponse
JSON SCHEMAImportResourcesRequest
JSON SCHEMAImportResourcesResponse
JSON SCHEMAInfoTypeTransformation
JSON SCHEMAIngestMessageRequest
JSON SCHEMAIngestMessageResponse
JSON SCHEMAKmsWrappedCryptoKey
JSON SCHEMALinkedEntity
JSON SCHEMAListAttributeDefinitionsResponse
JSON SCHEMAListConsentArtifactsResponse
JSON SCHEMAListConsentRevisionsResponse
JSON SCHEMAListConsentStoresResponse
JSON SCHEMAListConsentsResponse
JSON SCHEMAListDatasetsResponse
JSON SCHEMAListDicomStoresResponse
JSON SCHEMAListFhirStoresResponse
JSON SCHEMAListHl7V2StoresResponse
JSON SCHEMAListLocationsResponse
JSON SCHEMAListMessagesResponse
JSON SCHEMAListOperationsResponse
JSON SCHEMAListUserDataMappingsResponse
JSON SCHEMALocation
JSON SCHEMAMessage
JSON SCHEMANotificationConfig
JSON SCHEMAOperation
JSON SCHEMAOperationMetadata
JSON SCHEMAParsedData
JSON SCHEMAParserConfig
JSON SCHEMAPatientId
JSON SCHEMAPolicy
JSON SCHEMAProgressCounter
JSON SCHEMAPubsubDestination
JSON SCHEMAQueryAccessibleDataRequest
JSON SCHEMAQueryAccessibleDataResponse
JSON SCHEMARedactConfig
JSON SCHEMARejectConsentRequest
JSON SCHEMAReplaceWithInfoTypeConfig
JSON SCHEMAResources
JSON SCHEMAResult
JSON SCHEMARevokeConsentRequest
JSON SCHEMARollbackFhirResourceFilteringFields
JSON SCHEMARollbackFhirResourcesRequest
JSON SCHEMARollbackFhirResourcesResponse
JSON SCHEMASchemaConfig
JSON SCHEMASchemaGroup
JSON SCHEMASchemaPackage
JSON SCHEMASchemaSegment
JSON SCHEMASchematizedData
JSON SCHEMASearchResourcesRequest
JSON SCHEMASegment
JSON SCHEMASeriesMetrics
JSON SCHEMASetIamPolicyRequest
JSON SCHEMASignature
JSON SCHEMAStatus
JSON SCHEMAStreamConfig
JSON SCHEMAStudyMetrics
JSON SCHEMATagFilterList
JSON SCHEMATestIamPermissionsRequest
JSON SCHEMATestIamPermissionsResponse
JSON SCHEMATextConfig
JSON SCHEMATextSpan
JSON SCHEMATimePartitioning
JSON SCHEMAType
JSON SCHEMAUserDataMapping
JSON SCHEMAValidationConfig
JSON SCHEMAVersionSource
JSON SCHEMAScroll within the panel for all 147 ·
Examples 6
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Consentstore Example
EXAMPLEDataset Example
EXAMPLEDicomstore Example
EXAMPLEFhirstore Example
EXAMPLEHl7V2Store Example
EXAMPLEMessage Example
EXAMPLESecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Google Cloud Healthcare — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
← All providers · Data indexed from github.com/api-evangelist/google-cloud-healthcare · machine-readable index on apis.io