Cloud Healthcare API

gcpNoSQL databasegoogle-cloud-healthcare-api

Regional dataset holding FHIR, DICOM and HL7v2 clinical data stores.

Provider
gcp
Category
Data
Properties · 4 set by this component
propertytypevaluesrequiredkind defaultthis component
backupEnabledboolean—nofalseinherited
backupRetentionDaysinteger—no—inherited
bucketing · advancedboolean—nofalseinherited
conflictResolutionenumnone | last-writer-wins | vector-clock | app-mergeno—inherited
consistencyenumeventual | tunable | strongnoeventualinherited
customerManagedKeys · component propertyboolean—nofalseinherited
deidentification · component propertyboolean—nofalseinherited
encryptionAtRestboolean—nofalse▸ true
fhirVersion · component propertyenumdstu2 | stu3 | r4 | r5no—inherited
instancesinteger—no—inherited
managedboolean—nofalse▸ true
modelenumkey-value | wide-column | documentyes—▸ document
partitionKeystring—no—inherited
pubsubNotifications · component propertyboolean—nofalseinherited
quorumReads · advancedinteger—no—inherited
quorumWrites · advancedinteger—no—inherited
replicationenumsingle-region | multi-region-single-leader | multi-region-multi-leader | leaderlessnosingle-region▸ single-region
replicationFactorinteger—no—inherited
resourceVersioning · component propertyboolean—nofalseinherited
storeType · component propertyenumfhir | dicom | hl7v2nofhirinherited
tombstoneTtlDays · advancedinteger—no—inherited
Rules that apply · 2

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

multi-leader-store-without-conflict-policy

Multi-leader replication accepts concurrent writes in several regions. With no conflict resolution policy declared, divergent replicas are reconciled by accident rather than by design.

  • — all of these hold:
  • — the node's `replication` is "multi-region-multi-leader"
  • — any of these hold:
  • — the node's `conflictResolution` has no value
  • — the node's `conflictResolution` is "none"
read-heavy-path-without-cache

The design states a read-heavy workload and application servers read this datastore directly, yet the design has no cache anywhere. Every read pays a database round trip.

  • — all of these hold:
  • — the design requirement `traffic.readWriteRatio` is a number greater than 10
  • — the node has at least one synchronous incoming edge from an app-server
  • — this does not hold:
  • — the design contains a node of kind cache
Use it in a design
nodes:
  - { id: "cloud-healthcare-api", component: "google-cloud-healthcare-api" }
Other NoSQL database products · 46
ApsaraDB for HBasealibaba-apsaradb-hbasealibabacloudnosql-databaseApsaraDB for MongoDBalibaba-apsaradb-mongodbalibabacloudnosql-databaseLindormalibaba-lindormalibabacloudnosql-databaseTablestorealibaba-tablestorealibabacloudnosql-databaseAmazon CloudFront KeyValueStoreaws-cloudfront-keyvaluestoreawsnosql-databaseAmazon Cognito Syncaws-cognito-syncawsnosql-databaseAmazon DocumentDBaws-documentdbawsnosql-databaseAWS HealthLakeaws-healthlakeawsnosql-databaseAmazon Keyspaces (for Apache Cassandra)aws-keyspacesawsnosql-databaseAmazon DynamoDBdynamodbawsnosql-databaseAzure Cosmos DBazure-cosmos-dbazurenosql-databaseAzure DocumentDBazure-documentdbazurenosql-databaseAzure Health Data Servicesazure-health-data-servicesazurenosql-databaseAzure Managed Instance for Apache Cassandraazure-managed-cassandraazurenosql-databaseAzure Table Storageazure-table-storageazurenosql-databaseWorkers KVcloudflare-workers-kvcloudflarenosql-databaseApache Accumuloaccumulonosql-databaseAerospike Databaseaerospikenosql-databaseApache Cassandracassandranosql-databaseCouchbasecouchbasenosql-databaseApache CouchDBcouchdbnosql-databaseDataStax Enterprisedatastax-enterprisenosql-databaseFoundationDBfoundationdbnosql-databaseApache HBasehbasenosql-databaseMarkLogic Servermarklogicnosql-databaseMongoDBmongodbnosql-databaseMongoDB Atlasmongodb-atlasnosql-databaseGeneric NoSQL databasenosql-databasenosql-databaseNoSQL storenosql-storenosql-databaseOrientDBorientdbnosql-databaseRavenDBravendbnosql-databaseRethinkDBrethinkdbnosql-databaseRiak KVriaknosql-databaseScyllaDBscylladbnosql-databaseTiKVtikvnosql-databaseYDBydbnosql-databaseGoogle Cloud Bigtablebigtablegcpnosql-databaseGoogle Cloud Firestorefirestoregcpnosql-databaseFirebase Realtime Databasegoogle-firebase-realtime-databasegcpnosql-databaseFirestore in Datastore modegoogle-firestore-datastore-modegcpnosql-database
and 6 more → NoSQL database page
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# Cloud Healthcare API dataset: a regional container holding FHIR, DICOM and HL7v2 stores.
# "Cloud Healthcare API overview": each dataset is created in one storage location and its
# stores live in that same region. "Enable customer-managed encryption keys (CMEK)":
# Google Cloud encrypts the data at rest with Google-managed keys unless a Cloud KMS key
# is supplied at dataset creation, and the key cannot be changed afterwards.
schemaVersion: "1"
type: "component"
id: "google-cloud-healthcare-api"
kind: "nosql-database"
provider: "gcp"
docs: "https://docs.cloud.google.com/healthcare-api/docs/cmek"
defaults:
  model: "document"
  replication: "single-region"
  encryptionAtRest: true
  managed: true
properties:
  storeType:
    type: "enum"
    values: ["fhir", "dicom", "hl7v2"]
    default: "fhir"
  fhirVersion:
    type: "enum"
    values: ["dstu2", "stu3", "r4", "r5"]
  customerManagedKeys:
    type: "boolean"
    default: false
  deidentification:
    type: "boolean"
    default: false
  pubsubNotifications:
    type: "boolean"
    default: false
  resourceVersioning:
    type: "boolean"
    default: false

The same page as markdown, for an agent: /catalogue/components/google-cloud-healthcare-api.md